conv.

All stories
AIQuiet 9d · day 12

Programmer explores risks of learning code with AI before understanding fundamentals

A developer reflects on building production systems with LLMs while lacking deep comprehension of their own code.

What to know

  • A developer built a sophisticated system using LLMs without formal CS training, then discovered during production that gaps in understanding masked by AI assistance could undermine system reliability.
  • The core tension: LLMs can accelerate idea-to-code velocity, but may leave builders without the deep knowledge needed to maintain, debug, or own their systems long-term.
  • Experienced programmers worry LLMs could displace programmer jobs efficiently, risking 30-40% unemployment among knowledge workers with unpredictable economic consequences.
  • A practical distinction emerges: LLMs work best for falsifiable, verifiable tasks (code that runs or doesn't, is shorter or isn't) rather than open-ended design decisions.

Anonymous reader Self-taught programmer using LLMsMark Seemann Software engineer and economist

How it unfolded 2 developments, newest first · click a bar or a number to jump articlesposts

Peak 11 pieces in 3h at Sep 16, 4 AM; 43 pieces over 12 days (2 articles · 6 posts · 35 comments) Sep 16, 4 AM — 11 pieces · 2 articles · 2 posts · 7 comments — Hacker News 8, Newswires 2, Mastodon 1Sep 16, 7 AM — 8 pieces · 1 post · 7 comments — Hacker News 7, Mastodon 1Sep 16, 10 AM — 4 pieces · 4 comments — Hacker News 4Sep 16, 1 PM — 10 pieces · 1 post · 9 comments — Hacker News 9, Mastodon 1Sep 16, 4 PM — 2 pieces · 2 comments — Hacker News 2Sep 16, 7 PM — 2 pieces · 2 comments — Hacker News 2Sep 16, 10 PM — quietSep 17, 1 AM — quietSep 17, 4 AM — quietSep 17, 7 AM — 1 piece · 1 post — Lobsters 1Sep 17, 10 AM — quietSep 17, 1 PM — quietSep 17, 4 PM — quietSep 17, 7 PM — quietSep 17, 10 PM — 1 piece · 1 comment — Lobsters 1Sep 18, 1 AM — 2 pieces · 2 comments — Lobsters 2Sep 18, 4 AM — 1 piece · 1 comment — Lobsters 1Sep 18, 7 AM — quietSep 18, 10 AM — 1 piece · 1 post — Mastodon 1Sep 18, 1 PM — quietSep 18, 4 PM — quietSep 18, 7 PM — quietSep 18, 10 PM — quietSep 19, 1 AM — quietSep 19, 4 AM — quietSep 19, 7 AM — quietSep 19, 10 AM — quietSep 19, 1 PM — quietSep 19, 4 PM — quietSep 19, 7 PM — quietSep 19, 10 PM — quietSep 20, 1 AM — quietSep 20, 4 AM — quietSep 20, 7 AM — quietSep 20, 10 AM — quietSep 20, 1 PM — quietSep 20, 4 PM — quietSep 20, 7 PM — quietSep 20, 10 PM — quietSep 21, 1 AM — quietSep 21, 4 AM — quietSep 21, 7 AM — quietSep 21, 10 AM — quietSep 21, 1 PM — quietSep 21, 4 PM — quietSep 21, 7 PM — quietSep 21, 10 PM — quietSep 22, 1 AM — quietSep 22, 4 AM — quietSep 22, 7 AM — quietSep 22, 10 AM — quietSep 22, 1 PM — quietSep 22, 4 PM — quietSep 22, 7 PM — quietSep 22, 10 PM — quietSep 23, 1 AM — quietSep 23, 4 AM — quietSep 23, 7 AM — quietSep 23, 10 AM — quietSep 23, 1 PM — quietSep 23, 4 PM — quietSep 23, 7 PM — quietSep 23, 10 PM — quietSep 24, 1 AM — quietSep 24, 4 AM — quietSep 24, 7 AM — quietSep 24, 10 AM — quietSep 24, 1 PM — quietSep 24, 4 PM — quietSep 24, 7 PM — quietSep 24, 10 PM — quietSep 25, 1 AM — quietSep 25, 4 AM — quietSep 25, 7 AM — quietSep 25, 10 AM — quietSep 25, 1 PM — quietSep 25, 4 PM — quietSep 25, 7 PM — quietSep 25, 10 PM — quietYesterday, 1 AM — quietYesterday, 4 AM — quietYesterday, 7 AM — quietYesterday, 10 AM — quietYesterday, 1 PM — quietYesterday, 4 PM — quietYesterday, 7 PM — quietYesterday, 10 PM — quietToday, 1 AM — quietToday, 4 AM — quietToday, 7 AM — quietToday, 10 AM — quietToday, 1 PM — quietToday, 4 PM — quietToday, 7 PM — quiet 1–2
Sep 17Sep 18Sep 19Sep 20Sep 21Sep 22Sep 23Sep 24Sep 25yesterdaynow · 9:47 PM ET
  1. 2

    Mathematician endorses post's advice on verifiable LLM use

    A respondent praises the blog's implicit guidance: asking LLMs questions with objectively verifiable answers (e.g., code brevity, correctness) rather than open-ended design decisions.

    • The part about "falsifiable questions" explains why AI code reviews are usually okay and AI-generated code is not. It's relatively easy to check if a bug described by LLM exists, but (as you already said) it's hard to verify behavior of a complex vibecoded program.

      abareplacevibecoding9d ago3▲view on Lobsters ↗
    2 more of the top 3 · 33 posts in this stretch
    • Finally a thread to traumadump my anxieties!I have been trying to learn programming unsuccessfully for many years (I still ocasionally get a burst of energy, try something, then eventually abandon it halfway). In the end, I just accept that I don't have the kind of thinking that makes this effort enjoyable and I cannot achieve anything good.But…

      purpleflashingHacker News11d agoview on Hacker News ↗
    • ColinTheMathmo@mathstodon.xyz

      This is a thoughtful post: https:// blog.ploeh.dk/2026/09/16/on-le arning-programming-in-an-age-of-llms/ It's worth reading the whole things. It finishes with some great (implicit) advice: "I tend to ask them questions that yield verifiable answers. Can I make this Haskell expression more succinct? Any useful answer to such a question is a code…

      ColinTheMathmo@mathstodon.xyzMastodon11d agoview on Mastodon ↗
    all of them →
  2. 1

    Experienced programmer expresses ambivalence about LLMs' impact on programming competence

    The blog author, an economist with 30+ years in software, reveals skepticism about LLMs while acknowledging their power. He frames the broader concern: if LLMs displace programmer jobs efficiently, mass unemployment among knowledge workers could destabilize the economy.

    “It's usually when it impresses me the most that I resent it maximally.”
    — Mark Seemann, blog author
    1. first by HN Best, 11d ago · also HN Frontpage

    • I'm the author of Python Crash Course, and I got this exact same email this week. I was thinking of writing a public response as well, because any attempt to sincerely answer these questions takes something along the lines of a full post. It's also worth a public response because many people who are getting into programming for the first time…

      japhyrHacker News11d agoview on Hacker News ↗
    2 more of the top 3 · 3 posts in this stretch
    • I'm a software engineer, I do software development but also system maintenance, and I do handle networking and telephony systems, and work with some juniors. Working with AI is problematic. It can speed up you but at the same time delay you. For the system maintenance part sometimes you need to do a lot of stuff fast and in various machines and…

      duendefmHacker News11d agoview on Hacker News ↗
    • "The same kind of argument was used when China was admitted to the World Trade Organization. And indeed, lots of new jobs were created, just not in the Western world."China's entry into the WTO is really not a good evidentiary example for AI causing mass unemployment. Unemployment in the U.S. had already been increasing at the time, peaked soon…

      AnodicElegyHacker News11d agoview on Hacker News ↗
    all of them →
  3. background

    Developer describes building production system with LLMs despite knowledge gaps — A blog post shares a letter from someone who used LLMs to build a large TypeScript/JavaScript system without formal CS training, reporting initial success that later revealed fundamental misunderstandings when moving to production. The reader describes dependency on continued model assistance to fix cascading errors.

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