July 7, 2026
Bad code, hot drama
The difference between "today's task" and "accretive work"
When quick fixes become everyone else’s future headache
TLDR: The article says there’s a huge difference between a quick personal fix and software that other people must rely on for years. Commenters split between defending messy but useful shortcuts, mocking yet another AI debate, and joking that the real king of software is still Excel.
A spicy little philosophy-of-work post turned into a full-on comments-section cage match over a deceptively simple idea: sometimes a one-off fix for today’s problem is perfectly fine, and sometimes it becomes a slow-motion disaster for everyone forced to live with it later. The article argues that personal, homemade software can be useful and liberating, while mass-produced, boss-mandated artificial intelligence code can turn into dangerous junk. In plain English: the app you cobble together for yourself is not the same as software other people must depend on.
But the real fireworks came from the crowd. One side basically said, stop code-shaming quick solutions — if a rough-and-ready tool solves today’s task, it has value, even if it’s not built to last. Another camp rolled their eyes so hard they nearly rebooted, with one commenter delivering the icy dismissal: anything “about AI” is an instant “sigh and swipe left.” Ouch. Then came the anti-buzzword brigade, accusing the author of trying a little too hard to keep the “reverse centaurs” label alive.
And of course, the thread had jokes. The biggest crowd-pleaser was the evergreen meme that Excel is secretly the world’s most popular programming language, a reminder that much of modern work runs on messy spreadsheets, not elegant masterpieces. Meanwhile, the grimmer hot take was that companies may simply use AI to make workers go faster without making software any cheaper or better — just with more blame when things explode.
Key Points
- •The article argues that contradictory reports about AI-assisted coding can be explained by distinguishing between different kinds of work rather than treating them as one activity.
- •It defines “centaurs” as workers who direct their use of automation and “reverse centaurs” as workers made to serve automation systems.
- •The article presents vibe coding as part of a longer tradition of end-user software creation that includes shell scripting, AppleScript, HyperCard, and Visual Basic.
- •It argues that personal software written for oneself differs fundamentally from production code that others must use, maintain, and improve.
- •The article states that AI-driven coding practices in companies can create large amounts of technical debt when workers are reduced to validating machine-generated output.