There was that blog post.
And then that random youtube comment.
They’ve been on my mind for weeks now, mainly because they put words to something I’ve been feeling as a developer for the past two years or so: a quiet stagnation.
On top of that, there’s been this uncomfortable shift in focus as we transition from traditional software development into the “AI is going to take our jobs” era. Suddenly, we’re being nudged toward getting comfortable with not doing the exact tasks we’ve spent years mastering(even if they may seem mundane now).
As Nick Hodges rightly puts it in a post I riffed on:
“Ultimately, the next bottleneck will become proper thinking about what should be done. When you can do everything, deciding what not to do becomes the really difficult decision.”
It made something obvious finally click:
writing code — especially in the traditional sense — was always going to become less principal over time.
Not irrelevant, just less of the main event. Building products, however, isn’t going anywhere.
As tooling gets better and better, and leverage increases for the average person(especially non-developers), the real skill shifts toward thinking clearly, making good decisions, and putting together complete, working systems — not just shipping code in isolation.
As has been a mantra of mine for quite a while now:
“At any stage of proving that a concept exists, lies the possibility of building some kind of product — physical or digital, that solves a real-world problem.”
And when you think about it deeply, it raises a fair question:
does it really make sense to dabble in concepts and theory, or even just “practice coding” without building and applying it to real-world problems?
Building is where clarity comes from.
Building is where ideas get tested.
Building is where learning actually sticks.
So yeah — build, build, build.
Build complete, working products.
Just thinking out loud.
