The AI coding divide: craft lovers vs. result chasers

Coders clash: “art vs speed” as AI takes the wheel

TLDR: AI-assisted coding exposes a split between developers who value the artistry of hand-written code and those who just want results fast. The comments sparked a feud: some say the craft has shifted to guiding AI and teams, while others warn that unreviewed AI code is risky and costly.

The internet’s dev den is split like a reality show finale: craft lovers vs result chasers. The original article admits, “I’ve never been in it for elegance—I’m in it for what ships,” and many nodded. Simonw basically fist-bumped the thesis: motivations were invisible until AI made them obvious. But then the drama kicked in. Jacquesm crashed the party to say there’s not just one divide—there’s also money, security, and future maintenance to worry about. Translation: the real fight might be who pays when AI-generated code breaks.

CharlieDigital brought the “it’s still art” energy, saying the craft just moved up a level—away from typing code and toward writing clear guides and guardrails so the team (and AI) stops making a mess. Meanwhile, kalalakaka drew a hard line: unreviewed AI code and giant “PRs” (pull requests—bundles of changes) are corner-cutting, not craftsmanship. And the roast of the day? Elliotbnvl teased the post itself for “LLM-isms”—odd phrasing you get from AI—like spotting glitter glue on a Renaissance painting. The vibes: half mourning the old joy of late-night debugging, half thrilled to delegate drudgery to robots, and fully arguing over whether we’re sculpting clay… or just pressing the “make it go” button.

Key Points

  • The article argues AI-assisted coding makes visible a longstanding divide between craft-focused and outcome-focused developers.
  • It cites James Randall and Nolan Lawson to illustrate feelings of loss and mourning for traditional, hand-crafted coding practices.
  • The author describes a new fork in practice: letting machines write code while focusing on direction versus insisting on hand-crafting.
  • The author reports adapting to AI tools while retaining the ability to evaluate and review generated code for correctness and quality.
  • Puzzle-solving is described as shifting to a higher level of abstraction, consistent with past transitions in the author’s career.

Hottest takes

"It's still craft, its just that the craft is different." — CharlieDigital
"unreviewed AI code ... is absolutely cutting corners" — kalalakaka
"some painful LLM-os sticking out there :’(" — elliotbnvl
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.