conv.

All stories
AIActive · 42h

Essay 'AI Has No Wisdom and Neither Will You' ignites HN debate on vibe coding

A developer's blog post arguing AI-written code erodes maintainability and human skill tops Hacker News, splitting commenters between agreement and pushback.

What to know

  • The essay claims AI cannot be trained to value code maintainability because its costs only surface months or years after the fact, unlike immediately measurable reward signals.
  • It warns that developers who let AI write and read code for them will never build the intuition of an expert and will remain 'advanced beginners' indefinitely.
  • The post drew a large Hacker News discussion (178 comments) split between developers who share the institutional-knowledge concern and others who call the claim unfalsifiable, outdated, or already a losing argument against AI-driven development.

The dispute Whether code maintainability is a measurable, provable casualty of AI coding tools or an unfalsifiable claim being asserted too early to judge. · positions read across 48 posts and comments

many voices

AI-assisted coding is eroding institutional knowledge and engineering skill, much like manufacturing outsourcing hollowed out domestic expertise.

  • “The problem imo is the slow deterioration of institutional knowledge that offloading the mental task of wisdom gathering to AI is causing.”

    NalNezumi · Hacker News ↗
many voices

The essay's claims about maintainability are unfalsifiable or premature given how new coding agents are.

  • “We've had strong coding agents for less than a year. Anyone making such a definitive statement about how vibe-coded projects progress over time is basing it on guesswork, not evidence.”

    sobiolite · Hacker News ↗
some voices

This genre of anti-AI-coding warning is repetitive, preachy, and unlikely to persuade anyone.

  • “At least I did not find a new thought in that (granted, relatable) rant.”

    hypfer · Hacker News ↗
some voices

Manual coding and even architecture design are already becoming obsolete; resisting this is a conservative, losing position.

  • “As much as I'd love to believe it, it is now a conservative take. Sure, having a solid architecture in mind still matters right now, but manually writing code is completely unnecessary and, before long, even designing the architecture is…”

    addag · Hacker News ↗

Alexandru Nedelcu Software developer, blog authordavedx Hacker News commenterNalNezumi Hacker News commenter

How it unfolded 3 developments, newest first · click a bar or a number to jump articlespostscomments

Peak 16 pieces in one hour at Sep 22, 8 AM; 53 pieces over 43 hours (2 articles · 3 posts · 48 comments) Sep 22, 7 AM — 1 piece · 1 post — Lobsters 1Sep 22, 8 AM — 16 pieces · 2 articles · 2 posts · 12 comments — Hacker News 13, Newswires 2, Mastodon 1Sep 22, 9 AM — 13 pieces · 13 comments — Hacker News 13Sep 22, 10 AM — 3 pieces · 3 comments — Hacker News 3Sep 22, 11 AM — 4 pieces · 4 comments — Hacker News 2, Lobsters 2Sep 22, 12 PM — 4 pieces · 4 comments — Lobsters 4Sep 22, 1 PM — quietSep 22, 2 PM — 1 piece · 1 comment — Lobsters 1Sep 22, 3 PM — 1 piece · 1 comment — Lobsters 1Sep 22, 4 PM — 2 pieces · 2 comments — Lobsters 2Sep 22, 5 PM — quietSep 22, 6 PM — 1 piece · 1 comment — Lobsters 1Sep 22, 7 PM — quietSep 22, 8 PM — quietSep 22, 9 PM — 1 piece · 1 comment — Hacker News 1Sep 22, 10 PM — quietSep 22, 11 PM — quietYesterday, 12 AM — 1 piece · 1 comment — Lobsters 1Yesterday, 1 AM — quietYesterday, 2 AM — 1 piece · 1 comment — Lobsters 1Yesterday, 3 AM — quietYesterday, 4 AM — quietYesterday, 5 AM — quietYesterday, 6 AM — quietYesterday, 7 AM — quietYesterday, 8 AM — quietYesterday, 9 AM — quietYesterday, 10 AM — quietYesterday, 11 AM — quietYesterday, 12 PM — 1 piece · 1 comment — Lobsters 1Yesterday, 1 PM — 1 piece · 1 comment — Lobsters 1Yesterday, 2 PM — quietYesterday, 3 PM — quietYesterday, 4 PM — quietYesterday, 5 PM — quietYesterday, 6 PM — quietYesterday, 7 PM — 2 pieces · 2 comments — Lobsters 2Yesterday, 8 PM — quietYesterday, 9 PM — quietYesterday, 10 PM — quietYesterday, 11 PM — quietToday, 12 AM — quietToday, 1 AM — quiet 1–23
8 AM4 PMyesterday8 AM4 PMnow · 2:01 AM ET
  1. 3

    Commenters split over whether the claim is provable or already obsolete

    Hacker News commenters argued over whether maintainability can be measured at all, whether the essay's predictions are premature given how young agentic coding tools are, and whether resisting AI-written code is now a losing, 'conservative' position.

    “We've had strong coding agents for less than a year. Anyone making such a definitive statement about how vibe-coded projects progress over time is basing it on guesswork, not evidence.”
    — sobiolite
    • From what I understand, the things that empirically make code accessible to LLMs are the same things that make it accessible to humans - good documentation, consistent structure and style, robust test suites, use of well-known idioms, and so on. From the theoretical perspective, it also makes sense that many code maintenance benchmarks and…

      dulakurant,vibecoding1d ago17▲view on Lobsters ↗
    2 more of the top 3 · 41 posts in this stretch
    • I believe many of us here knows that the idea of a simple prompt to make something more than a sketch or a prototype don’t really work.Unless you steer and understand what an LLM will produce, you will end up with something that possible ”works” that has no future plans baked in. Suno generated music has a very unpleasant feeling of sounding like…

      EastLondonCoderHacker News1d agoview on Hacker News ↗
    • > In the future we will see more and more companies proudly boasting their “NO-AI” policy as a competitive advantage. And they will be right. I appreciate the prediction, but I think it’s definitely wrong, even though I’m not someone who advocates against reading the code. I don’t know how to make it testable, but I’m confident that the use of AI…

      hyperpaperant,vibecoding1d ago16▲view on Lobsters ↗
    all of them →
  2. 2

    Post hits Hacker News front page, cross-posted to Lobsters

    The essay was submitted to Hacker News (score 138, 178 comments) and independently cross-posted to Lobsters and syndicated via the HN Frontpage RSS feed the same morning.

    “Fact is, vibe-coded projects devolve over time into an unmaintainable mess.”
    — Alexandru Nedelcu, blog author · source
    • There's a continuum between "vibe coded by someone with no technical knowledge or inclination" and "hand written domain driven design development". You can absolutely use coding agents AND have maintainable code. But yes, the coding agents will not magically make everything maintainable if you don't tell them to."Code maintainability and good…

      davedxHacker News1d agoview on Hacker News ↗
    2 more of the top 3 · 7 posts in this stretch
    • > You can absolutely use coding agents AND have maintainable code. But yes, the coding agents will not magically make everything maintainable if you don't tell them to.The trillion dollar question is how you do this, if your employees do not care (they are optimising for salary & time spent not code quality) and you have no way of telling apart AI…

      abroszka33Hacker News1d agoview on Hacker News ↗
    • Tbf, at this point, this has been said ad-nauseam.At least I did not find a new thought in that (granted, relatable) rant."This is bad and you are bad" requires people to not defend their reality through rationalization, but the point we're at with AI right now is driven by exactly that. So this is at best highly ineffective at reaching the people…

      hypferHacker News1d agoview on Hacker News ↗
    all of them →
  3. 1

    Nedelcu publishes essay warning vibe coding produces unmaintainable code

    The blog post argues AI models cannot be trained to value long-term code maintainability because its costs only appear months or years later, and warns that developers who rely on AI to write and read code will never develop expert intuition.

Also covered reported alongside — the timeline has no entry for these yet

  1. first by HN Best, 1d ago · also HN Frontpage

What people are saying 18 voices from 2 sites · best of 48 · verbatim

Still unanswered
  • How, concretely, should code maintainability be measured if not by existing metrics like cyclomatic complexity?
  • Will companies actually adopt 'no-AI' policies as a competitive/quality advantage, as the essay predicts?