A senior developer with thirty years of experience argues that programming education has it backwards. Bootcamps teach language syntax in six weeks, but the skills that actually make a developer senior—understanding system architecture, data flow, and which decisions become permanent—take a decade to develop and almost nobody teaches them at the entry level.

The author illustrates this with a telling anecdote: reviewing a junior's pull request in an unfamiliar language, they spotted the code was fundamentally flawed—five lines that should have been one, with data unnecessarily cycling through transformations—despite not knowing the syntax. The junior had learned the language; the author had learned to program. This distinction matters because most introductory courses focus on syntax, standard libraries, and idiomatic patterns, treating these as programming itself.

What senior developers actually do daily—reading code, tracing data through layers, debugging systematically, recognizing which decisions become expensive to change—appears in no beginner curriculum. The author recalls a VB6 developer in 1997 who, after two years of writing correct but flat code, suddenly grasped event-driven thinking and their code transformed. That shift, understanding what kind of system you're inside, cannot be put on a slide.

AI tools like Claude Code now amplify this problem. They generate plausible code quickly, but without judgment to distinguish plausible from correct, developers ship bad code faster than ever. The bottleneck was never typing speed—it was knowing what code should be written in the first place.