I know so many devs I’ve talked to who treat the languages they work in as a black box. They write certain words, something happens, and that’s good enough. But why it happens? Who cares. They have families and hobbies, and in the grand scheme of things, it works at the end of the day.
But to me, that’s like driving. You can be aware, informed, and skilled—or you can choose to drive however you can “get away” with.
Without being informed, you might need to take a driver’s test—and you’d fail. Without being aware, you might cause an accident. Without practice, your skill won’t hold up in a tough spot. But most importantly, unless you choose to understand both the how and the why behind it all, the person you’re most consistently putting at a disadvantage is you.
I want to be the person who understands more wholly why things are organized and function the way they do. Not out of fear of those things I mentioned above, but because of a genuine curiosity that transforms a job with tasks into an incubator for growing passion. Code is a wonderful outlet for someone who has a passion for understanding. A curious spirit will always find the inner workings of code intriguing—especially code that closely models real life and adds a touch of magic. It’s like getting into a car and understanding it deeply: you can then go fast, pull off amazing stunts, enjoy the ride fully, and come out unscathed.
So what is this blog? It’s a bit like a garden bed for my passion. I don’t want to lose it in a crowd of “why care?”. Here, I can cultivate and grow it into something beautiful—my little code garden. It’s a quiet resistance against the doldrums of apathy toward the craft.
This site is 99% for me. Explaining software concepts and topics in a narrative form helps solidify my understanding and keeps me engaged in the meaning of what code can enable me to explore—not just the syntax and the tasks.
The remaining 1% is for you—to come along and maybe spark a little curiosity too.
Leave a Reply