I have a love-hate relationship with the “fundamentals”. Be it learning to code, picking up new skills and knowledge, developing new habits, I’m the impatient sort who loves to jump right in and try things out, even if I don’t know what I’m doing. I hated how veteran gatekeepers of any field/niche would police newbies by using “the fundamentals” as some sort of an entrance exam. I felt that learning the fundamentals through some 100-hour boring course hinders more than it helps. But sometimes, that’s when the long arm of the fundamentals come back to bite me. With good reason.
I find that such scenarios—of inflated perceptions of difficulty unfolding into a laughable realisation of the solution—are usually signs that the fundamentals are missing. If I had taken the boring and labourious yet effective approach of debugging by commenting out code bit by bit, I wouldn’t have needed 4am late nights and three wasted days. Yet, here I am, deeply humbled due to a combination of newbie inexperience, impatience with the fundamentals, and that just-want-to-do-my-own-way personality.
It’s a great learning point, and even greater validation of why the fundamentals matter, not just in coding but any pursuit of skill or knowledge. Not that everyone now has to know the fundamentals before starting any pursuit. But more like the fundamentals cannot be ignored, and incidents like this are signals that I need to brush up on them, rather than haughtily brushing them off like I knew better.
This post was first published on Lifelog.