GoKawiil0x0C │ 2026.05.01 │ 9 min read │ programming · education · software-engineering · opinion · career · learning · good-practice · mentorship
A bootcamp can teach you the syntax of a language in six weeks. The part that takes a decade is everything else: where the seams go, where the data flows, which decisions you are stuck with for the life of the codebase. This is a senior developer's argument for what learners should actually be looking for, after thirty years of watching the difference.
Good developers learn to program. Most courses teach a language.
A few years back I was looking over a junior's pull request in a language I had never written professionally. I could not have told you the standard library off the top of my head. I had to look up the syntax for a lambda. And I knew, without running the code, that the function was wrong.
It was five lines that should have been one. The shape was wrong. The data went out, came back, got reshaped, came back again, and finally landed where it had started, lightly bruised. The variable names were fine. The syntax was fine. The function did what it claimed to do. It was still wrong, because the thing it was doing was not the thing that should have been done at that point in the program.
I could see that because I have been programming for a long time. The junior could not see it because they had been taught a language. Those are not the same skill, and the gap between them is the part of this job that almost nobody is teaching at the entry level.
Language is not the bottleneck
Almost every introductory course, video, and bootcamp on the market teaches the syntax of a particular language and calls that programming. It isn't. Programming is the part that is the same across languages: how a system goes together, where the seams are, what data flows where, which decisions are cheap to change next month and which decisions you are going to be stuck with for the life of the codebase.
I have written about the deeper version of this argument elsewhere. The book chapter on the decline of foundational understanding in modern programming education lays out what is actually being lost: mechanical empathy, an honest mental model of the machine underneath, the historical context that explains why systems are shaped the way they are. That essay is the structural argument. This post is the field guide that comes after it. If you have read the chapter and asked, "fine, so what should a learner do about it," this is that answer.
What I think happened in 1997
... continue reading