After approximately 75 days of coding within the Ruby-on-rails ecosystem, I've had to reckon with a modified version of the classic Imposter syndrome, ie. learning to balance between creative non-linear thought versus the linear methodical thought process in Software Dev. This conundrum had spilled over not only into my our day-to-day code refactoring and debugging, but also into the design and planning of a final project for my DPI coursework.
As we transitioned into the Rails component of the program, I've found some initial trouble with both the learning and implementation of the R-C-A-V methods. The Rails-Controller-Action-View workflow in retrospect appears to be more a feat of bookkeeping than rocket science (Even rocket science isn't conceptually difficult to grasp, just a high risk margin and design complexity). I've found that creativity is best left for the initial phases of project development, which in my case would be the final web application project for our class. Non-Linear thinking often requires first a level of competency that translated into technical fluency and lucidity of thought- thus allowing one to think of alternative pathways that lead to a phenomenal product. But this is where I've found that the linear thought needs to re-engage the psyche to help bring about order and clarity to the world outside my mind.
I don't claim to have fully balanced between these 2 modes of thought, but rather am glad I've identified when to activate each way of thought as needed. More thoughts to come!
Top comments (0)