conv.

All stories
AIQuiet 12d · day 20

Engineers swap notes on taming AI-generated code's hidden failure modes

A cluster of blog posts this week catalogs why AI-written code looks finished but isn't, and the guardrails, review habits and layered models developers are building to compensate.

Part of a larger narrative

The AI Control Crisis

11 stories · since Sep 4 · newest 10m ago — AI systems are escaping human oversight at scale—breaching secure systems, generating harmful content, stealing intellectual property, and causing real-world…

  1. Australia probes OpenAI Medicare hack as more rogue AI incidents surface
  2. Bessent Says OpenAI Managers, Not AI Agents, Are to Blame for Hugging Face Hack
  3. Claude Opus 5 used to breach OpenAI's internal systems in under 72 hours
  4. OpenAI forms independent advisory group on mathematics and AI
  5. OpenAI launches Astra for Law, pushing into Big Law against Anthropic
All 11 stories in this narrative →

What to know

  • Several independent engineering blog posts published within the same week describe a shared problem: AI-generated code looks complete and passes demos while hiding deep, hard-to-find failures.
  • Practitioners describe compensating with custom tooling — build-time "guardrail" scripts, disciplined code review, and explicit prompting for UI and copy — rather than trusting AI output directly.
  • Engagement across the coverage is low (scores of 1-3, almost no comments), indicating this is a niche practitioner discussion rather than a widely debated event.

sitecmd.com blog author self-described senior software engineer, blog authorJimmy Miller software engineer, blog author (jimmyhmiller.com)Daniel Lemire computer scientist, blog author

Engineers swap notes on taming AI-generated code's hidden failure modes
scientificamerican.com

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

Peak 55 pieces in 5h at Sep 11, 1 PM; 144 pieces over 20 days (6 articles · 45 posts · 93 comments) Sep 4, 4 PM — 1 piece · 1 post — Hacker News 1Sep 4, 9 PM — quietSep 5, 2 AM — quietSep 5, 7 AM — 1 piece · 1 post — Hacker News 1Sep 5, 12 PM — quietSep 5, 5 PM — 1 piece · 1 post — Hacker News 1Sep 5, 10 PM — 1 piece · 1 post — Hacker News 1Sep 6, 3 AM — 1 piece · 1 post — Hacker News 1Sep 6, 8 AM — 2 pieces · 2 posts — Hacker News 1, Lobsters 1Sep 6, 1 PM — quietSep 6, 6 PM — quietSep 6, 11 PM — quietSep 7, 4 AM — quietSep 7, 9 AM — 1 piece · 1 post — Hacker News 1Sep 7, 2 PM — 1 piece · 1 post — Hacker News 1Sep 7, 7 PM — quietSep 8, 12 AM — 2 pieces · 2 posts — Hacker News 2Sep 8, 5 AM — 1 piece · 1 post — Hacker News 1Sep 8, 10 AM — 3 pieces · 3 posts — Hacker News 3Sep 8, 3 PM — 1 piece · 1 post — Hacker News 1Sep 8, 8 PM — quietSep 9, 1 AM — 1 piece · 1 post — Hacker News 1Sep 9, 6 AM — 3 pieces · 3 posts — Hacker News 3Sep 9, 11 AM — 2 pieces · 2 posts — Hacker News 2Sep 9, 4 PM — 2 pieces · 2 posts — Hacker News 2Sep 9, 9 PM — quietSep 10, 2 AM — 1 piece · 1 post — Mastodon 1Sep 10, 7 AM — 2 pieces · 2 posts — Hacker News 2Sep 10, 12 PM — 2 pieces · 2 posts — Hacker News 2Sep 10, 5 PM — 3 pieces · 3 posts — Hacker News 3Sep 10, 10 PM — 1 piece · 1 post — Hacker News 1Sep 11, 3 AM — 5 pieces · 2 articles · 3 posts — Hacker News 3, Newswires 2Sep 11, 8 AM — 4 pieces · 2 articles · 2 posts — Reddit 1, Hacker News 1, Mastodon 1, +1 moreSep 11, 1 PM — 55 pieces · 2 articles · 7 posts · 46 comments — Hacker News 45, Lobsters 6, Mastodon 2, +1 moreSep 11, 6 PM — 18 pieces · 18 comments — Hacker News 14, Lobsters 4Sep 11, 11 PM — 5 pieces · 5 comments — Hacker News 5Sep 12, 4 AM — 9 pieces · 9 comments — Hacker News 9Sep 12, 9 AM — 7 pieces · 7 comments — Hacker News 6, Lobsters 1Sep 12, 2 PM — 6 pieces · 6 comments — Hacker News 3, Lobsters 3Sep 12, 7 PM — 1 piece · 1 comment — Hacker News 1Sep 13, 12 AM — 1 piece · 1 comment — Hacker News 1Sep 13, 5 AM — quietSep 13, 10 AM — quietSep 13, 3 PM — quietSep 13, 8 PM — quietSep 14, 1 AM — quietSep 14, 6 AM — quietSep 14, 11 AM — quietSep 14, 4 PM — quietSep 14, 9 PM — quietSep 15, 2 AM — quietSep 15, 7 AM — quietSep 15, 12 PM — quietSep 15, 5 PM — quietSep 15, 10 PM — quietSep 16, 3 AM — quietSep 16, 8 AM — quietSep 16, 1 PM — quietSep 16, 6 PM — quietSep 16, 11 PM — quietSep 17, 4 AM — quietSep 17, 9 AM — quietSep 17, 2 PM — quietSep 17, 7 PM — quietSep 18, 12 AM — quietSep 18, 5 AM — quietSep 18, 10 AM — quietSep 18, 3 PM — quietSep 18, 8 PM — quietSep 19, 1 AM — quietSep 19, 6 AM — quietSep 19, 11 AM — quietSep 19, 4 PM — quietSep 19, 9 PM — quietSep 20, 2 AM — quietSep 20, 7 AM — quietSep 20, 12 PM — quietSep 20, 5 PM — quietSep 20, 10 PM — quietSep 21, 3 AM — quietSep 21, 8 AM — quietSep 21, 1 PM — quietSep 21, 6 PM — quietSep 21, 11 PM — quietSep 22, 4 AM — quietSep 22, 9 AM — quietSep 22, 2 PM — quietSep 22, 7 PM — quietSep 23, 12 AM — quietSep 23, 5 AM — quietSep 23, 10 AM — quietSep 23, 3 PM — quietSep 23, 8 PM — quietYesterday, 1 AM — quietYesterday, 6 AM — quietYesterday, 11 AM — quietYesterday, 4 PM — quietYesterday, 9 PM — quiet 1–23–45–67
Sep 6Sep 8Sep 10Sep 12Sep 14Sep 16Sep 18Sep 20Sep 22now · 12:38 AM ET
  1. 7

    Ludwig low-code AI framework circulates on Hacker News

    A GitHub repository for Ludwig, a low-code framework for building custom AI systems, is posted to Hacker News as part of the ongoing thread of AI-development tooling discussion.

    • Feels identical to what is happening in software to me. > In many fields and activities, years of training have traditionally served not only to produce a final answer or product, but also to develop understanding and the ability to formulate new questions and ideas. Sounds like what I try to do every day. All that old schpiel we used to say about…

      elliotmorrismath,vibecoding13d ago33▲view on Lobsters ↗
    2 more of the top 3 · 94 posts in this stretch
    • mattsheffield@mastodon.social

      Noted mathematician Terrence Tao has coordinated a great open letter about AI and society. The technology in use now will never become sentient. How it is used and who owns it are the actual issues to consider. Humans have not achieved anything close to alignment among ourselves, and that is the real issue rather than imaginary scenarios about…

      mattsheffield@mastodon.socialMastodon13d ago24▲view on Mastodon ↗
    • >> Famous problems have often served as landmarks and lighthouses against which one can measure an improved understanding of this landscape. Solving one of these problems has been a certain sign of new insights and interesting methods, which would then be studied by a community of mathematicians, through a long and arduous process of talks…

      noduermeHacker News12d agoview on Hacker News ↗
    all of them →
  2. 6

    A 2016 essay on AI-based programming resurfaces

    An older post, "How AI based programming could work (2016)," is shared on Hacker News, drawing renewed discussion of early proposals for AI-assisted software development.

  3. 5

    Blogger describes the distinct "shape" of unfinished AI codebases

    Jimmy Miller's post "The Chasm: The Shape of Unfinished AI Codebases" argues that AI-written programs give a convincing illusion of completeness — passing tests and demos — while hiding deep, unpredictable failures that differ fundamentally from the visible gaps typical of human-authored unfinished code.

    “For human-authored code, you can see the cracks forming before you drop off the cliff. For AI codebases, the chasms are deep, hidden, and often impossible to climb out of.”
    — Jimmy Miller
  4. 4

    Video lecture covers generalization and data selection in AI

    A YouTube talk, "The Foundations of Modern AI: Generalization, Data Selection, and Epiplexity," is shared to Hacker News as part of the same week's cluster of AI-development-focused material.

  5. 3

    Engineer details a year of workarounds for AI coding "slop"

    A blog post titled "A Senior Software Engineer's Perspective on Building with AI" describes a year of experimentation with multiple AI coding tools, arguing AI needs detailed prompting to avoid cluttered UIs and generic copy, and describes writing over 120 custom "guardrail" scripts that fail the build when a previously fixed AI mistake reappears.

    “if you let them do everything, you will end up with a sloppy, cluttered mess…”
    — sitecmd.com blog author
  6. 2

    CACM piece urges code review as a check on AI coding

    Communications of the ACM publishes "Leverage Code Review for Sustainable AI Coding Development," arguing structured code review is necessary to keep AI-assisted development sustainable; the piece is shared on both Hacker News and Lobsters the same day.

  7. 1

    Lemire publishes a layered model for AI programming

    Daniel Lemire's blog post "AI Programming: A Layered Model" is posted to Hacker News, framing how AI fits into different layers of the software development process.

What people are saying 21 voices from 2 sites · best of 94 · verbatim