AI demands more engineering discipline. Not less

Overall reaction to the article

• Many found the piece verbose, meandering, and light on concrete conclusions; some suspected “AI slop” writing.
• A minority liked the central idea (AI ⇒ more discipline, not less) but felt the argument was muddled or wishy‑washy.
• Readers noted tension between “AI is existentially important” rhetoric and hand‑wavy treatment of trade‑offs.

Code vs. specs, docs, and prompts

• One core debate: should code remain the “primary artifact,” or should specs, tests, and prompts become the main objects of review while code is disposable?
• Several argue code is the only unambiguous, executable specification and thus must stay central.
• Others support shifting knowledge into design docs, ADRs, tests, and prompt histories, letting AI regenerate code as an implementation detail.
• Skeptics warn that coarser abstractions and LLM “specs” are not yet reliable enough to skip detailed code review.

AI code quality, “slop,” and verification

• Strong sentiment that AI produces working but alien, overcomplicated, or brittle code that is painful to read and maintain.
• Supporters counter that with solid design, constraints, and tests, AI can produce high‑quality, defensive code and accelerate non‑novel work.
• Broad agreement that the bottleneck is now evaluation and verification, not code generation.
• Some foresee systems that validate properties and tests instead of humans reading most code; others doubt this is realistically achievable without stable, human‑understandable code.

Lines of code, productivity, and technical debt

• Long‑running HN norm: removing code is a marker of seniority. Many defend this more strongly in the AI era.
• AI enables huge PRs and floods of “superficially plausible” code and documentation, making it harder to identify who truly understands systems.
• Using LoC or PR count as productivity metrics is seen as especially broken now.
• Multiple comments predict a massive new form of technical debt from AI‑generated code and documents, likened to asbestos or “technical bankruptcy.”

Discipline, roles, and incentives

• Many agree AI can demand more discipline: better specs, tests, observability, and provenance (e.g., capturing prompts and design intent).
• At the same time, AI makes it easier to appear productive without understanding, especially under executive pressure to “use AI everywhere.”
• Some expect SWE roles to shift toward architecture, documentation, and test design rather than vanish; others argue unskilled + AI is a new systemic risk, especially for juniors.