May 1, 2026
Syntax Sells, Thinking Wins
Good developers learn to program. Most courses teach a language
Coders Are Fighting Over Whether Classes Teach Thinking or Just Button-Pushing
TLDR: The article argues that many classes teach people to memorize a coding language instead of teaching real problem-solving. Commenters split fast: some praised that as painfully true, while others insisted you must learn one real language first before the deeper thinking can begin.
A spicy essay about programming education has set off a very familiar internet war: are beginners being taught how to solve problems, or just how to memorize a language’s rules? The writer’s big claim is that plenty of courses teach people to type the right symbols, but not to see when code is clunky, wasteful, or solving the wrong problem. In plain English: someone can write something that “works” and still miss the smarter way to do it.
And the comments? Absolute catnip. One camp basically yelled, “Yes! This is exactly the problem!” One teacher from France jumped in to say their degree already teaches ways of thinking rather than worshipping one language, flexing that students touch around 10 languages and several styles of problem-solving early on. Another commenter got nostalgic about old-school university “weed out” classes from the post-dotcom era, when schools were apparently trying to filter out dreamers who thought making a website meant instant riches.
But not everyone bought the sermon. The pushback was immediate: you can’t learn to think without first learning a language, argued one commenter, sparking the classic chicken-and-egg brawl. Others leaned into the everyday grind, saying real programming is mostly reading messy old code and untangling past decisions like a detective at a crime scene. Even the jokes had bite: one commenter described bad code as if data got sent on a pointless little round-trip and came back “lightly bruised.” Ouch.
Key Points
- •The article distinguishes learning a programming language from learning how to program across systems and contexts.
- •It argues that many introductory educational formats focus on syntax and tools rather than system structure, data flow, and software design judgment.
- •The author uses a code review example to show that code can be syntactically correct yet still be the wrong solution for a program’s structure.
- •A Visual Basic 6 anecdote is used to show how a developer improved after understanding event-driven systems rather than after learning more syntax.
- •The article says standard instruction often covers syntax, libraries, type systems, build tools, and package managers, but not the deeper judgment that develops through experience.