March 16, 2026
Vibes vs brains: choose your fighter
On The Need For Understanding
Vibe Coding vs Knowing Stuff: Devs Are Fighting About It
TLDR: A debate over whether coding should be about true understanding or quick experimentation reignited after a classic MIT perspective resurfaced. Commenters split: some reject “vibe coding” and AI-driven shortcuts, while others note real-world pressures favor speed, with a few insisting you can still read the code and truly know it.
A throwback quote from MIT legend Gerald Sussman lit a bonfire under programmers this week, after a reflective post pushed the idea that modern coding is less “build from parts you understand” and more “poke it until it works.” Cue chaos. One camp came in hot with anti-"vibe coding" energy — “understanding” isn’t optional, it’s the job. Another camp said the world is messier now: docs are bad, stacks are huge, and yes, sometimes you experiment your way to an answer.
The nostalgia angle was strong: folks reminisced about MIT’s old 6.001 class built on Scheme (a classic teaching language behind SICP), where you learned to truly grasp every piece. But the spicy takes stole the show. One commenter roasted the AI craze: “In the world the ‘AI bros’ want, understanding is a hobby,” sparking replies about speed-at-all-costs culture. Another pushed back with a DIY energy: just read the library code and figure it out — you still can. A nuanced voice noted the split: safety-critical fields (think planes) demand deep understanding, while fast-moving apps often don’t.
Meanwhile, meta-jokes rolled in about the essay being "human, repetitive, and that’s the point". Verdict? The community’s split between romance for understanding and the reality of shipping fast — with memes, side-eyes, and a little heartbreak for lost craft.
Key Points
- •The article reacts to Andy Wingo’s Mastodon post summarizing Gerald Sussman’s view on modern programming’s reliance on probing third-party libraries.
- •It recounts Sussman’s explanation for MIT’s shift away from Scheme in its introductory course, emphasizing a change from fully understood components to opaque software stacks.
- •The author acknowledges today’s software complexity and inadequate documentation but disputes the idea that deep understanding is no longer attainable.
- •A primary source video of Sussman discussing the course change is linked and timestamped.
- •The author outlines their own progression from BASIC on 8-bit machines to learning VGA via BBS tutorials and using tools like Microsoft QuickC, illustrating a path toward deeper system understanding.