Reading the code may be the wrong bar. The durable skill is reading the architecture: what the system should do, where it breaks, what counts as done. That spec-level judgment is what separates builders who ship from builders who pile up code nobody can review. Are you seeing non-technical builders actually develop it, or just prompt faster?
Agreed, I think it's ultimately about the shape of things, not being able to read the minutia of every line of code. JavaScript, JSX, and TSX are so cryptic that it does require some familiarity with the language. I wish a more human-readable language like Python had become the language of the web, but here we are!
My path went from coding on a Commodore 64 to studying engineering, and finally landing in product. But no matter where you sit in the tech ecosystem or how long you've been at it, refreshers like this are gold.
At the end of the day, if you don't understand what you are building and how it works under the hood, even the best AI tools won't save you, at least for now. Thanks for writing this!
Vjeko, sorry for the slow reply, just seeing this now!
Love the journey from Commodore 64 to product, that's a great arc. I was always jealous of the folks with Commodores. And you're so right about understanding what's under the hood. The tools will keep changing, but that foundation is what actually compounds over time. Thanks for reading and for taking the time to share this.
Reading the code may be the wrong bar. The durable skill is reading the architecture: what the system should do, where it breaks, what counts as done. That spec-level judgment is what separates builders who ship from builders who pile up code nobody can review. Are you seeing non-technical builders actually develop it, or just prompt faster?
Agreed, I think it's ultimately about the shape of things, not being able to read the minutia of every line of code. JavaScript, JSX, and TSX are so cryptic that it does require some familiarity with the language. I wish a more human-readable language like Python had become the language of the web, but here we are!
This was a fantastic read from start to finish.
My path went from coding on a Commodore 64 to studying engineering, and finally landing in product. But no matter where you sit in the tech ecosystem or how long you've been at it, refreshers like this are gold.
At the end of the day, if you don't understand what you are building and how it works under the hood, even the best AI tools won't save you, at least for now. Thanks for writing this!
Vjeko, sorry for the slow reply, just seeing this now!
Love the journey from Commodore 64 to product, that's a great arc. I was always jealous of the folks with Commodores. And you're so right about understanding what's under the hood. The tools will keep changing, but that foundation is what actually compounds over time. Thanks for reading and for taking the time to share this.