conv.

All stories
AIQuiet 12d · day 14

Essay predicting AI turns coders into "product engineers" ignites hype debate

A widely shared blog post arguing AI agents will absorb the full software lifecycle draws both agreement and accusations of industry hype.

What to know

  • Seldo's essay argues agents already write code well but remain weak at review, testing and deployment, and predicts that gap closes within a decade, turning developers into "product engineers."
  • The forecast rests on two flagged assumptions: agent weaknesses are temporary, and software demand is effectively infinite, so there's no lasting developer glut.
  • Lobsters commenters split between calling the "singularity" framing AI-industry hype and defending the incremental-improvement thesis with cited data.
  • A parallel strand of commenters worries the shift is hollowing out computer science as an academic and craft discipline, separate from the jobs question.

The dispute Whether agents' current weakness at review, testing and deployment is a temporary gap that will close (the essay's thesis) or a structural limit exposed by AI-industry marketing. · positions read across 27 posts and comments

many voices

The essay's assumption that agents will inevitably master review, testing and deployment is unproven AI-industry hype dressed as forecasting.

  • “This singularity view about AI/LLM capabilities is just advertising, knowingly or not.”

    Halkcyon · Lobsters ↗
some voices

Agents are already improving steadily at review and maintenance, and the essay's trajectory is backed by real data, not just hype.

  • “The linked article addresses that: > For reviewing and maintenance, agents are clearly not there yet, but the data shows them on an upward trajectory.”

    simonw · Lobsters ↗
some voices

This shift is hollowing out computer science as an academic discipline and craft, not just changing what programmers do day to day.

  • “It does seem like the entire field of Computer Science is dying (and no one cares) unless you've managed your way into a PhD and academia.”

    dysoco · Lobsters ↗

“The demand for software, at least inside my 10 year horizon, is for practical purposes infinite, or software developers wouldn't be as highly paid as they are.”

seldo, Author · seldo.com · Sep 13

seldo Author of the essaytante Mastodon criticHalkcyon Lead skeptic in the Lobsters threadsimonw Lobsters commenter

How it unfolded 5 developments, newest first · click a bar or a number to jump postscomments

Peak 13 pieces in 4h at Sep 14, 9 AM; 33 pieces over 14 days (8 posts · 25 comments) Sep 13, 9 PM — 1 piece · 1 post — Mastodon 1Sep 14, 1 AM — 1 piece · 1 post — Hacker News 1Sep 14, 5 AM — 5 pieces · 2 posts · 3 comments — Lobsters 4, Mastodon 1Sep 14, 9 AM — 13 pieces · 1 post · 12 comments — Lobsters 12, Hacker News 1Sep 14, 1 PM — 4 pieces · 1 post · 3 comments — Lobsters 3, Reddit 1Sep 14, 5 PM — 3 pieces · 3 comments — Reddit 2, Lobsters 1Sep 14, 9 PM — 2 pieces · 1 post · 1 comment — Hacker News 1, Lobsters 1Sep 15, 1 AM — quietSep 15, 5 AM — 2 pieces · 2 comments — Lobsters 2Sep 15, 9 AM — quietSep 15, 1 PM — quietSep 15, 5 PM — 1 piece · 1 comment — Lobsters 1Sep 15, 9 PM — quietSep 16, 1 AM — 1 piece · 1 post — Hacker News 1Sep 16, 5 AM — quietSep 16, 9 AM — quietSep 16, 1 PM — quietSep 16, 5 PM — quietSep 16, 9 PM — quietSep 17, 1 AM — quietSep 17, 5 AM — quietSep 17, 9 AM — quietSep 17, 1 PM — quietSep 17, 5 PM — quietSep 17, 9 PM — quietSep 18, 1 AM — quietSep 18, 5 AM — quietSep 18, 9 AM — quietSep 18, 1 PM — quietSep 18, 5 PM — quietSep 18, 9 PM — quietSep 19, 1 AM — quietSep 19, 5 AM — quietSep 19, 9 AM — quietSep 19, 1 PM — quietSep 19, 5 PM — quietSep 19, 9 PM — quietSep 20, 1 AM — quietSep 20, 5 AM — quietSep 20, 9 AM — quietSep 20, 1 PM — quietSep 20, 5 PM — quietSep 20, 9 PM — quietSep 21, 1 AM — quietSep 21, 5 AM — quietSep 21, 9 AM — quietSep 21, 1 PM — quietSep 21, 5 PM — quietSep 21, 9 PM — quietSep 22, 1 AM — quietSep 22, 5 AM — quietSep 22, 9 AM — quietSep 22, 1 PM — quietSep 22, 5 PM — quietSep 22, 9 PM — quietSep 23, 1 AM — quietSep 23, 5 AM — quietSep 23, 9 AM — quietSep 23, 1 PM — quietSep 23, 5 PM — quietSep 23, 9 PM — quietSep 24, 1 AM — quietSep 24, 5 AM — quietSep 24, 9 AM — quietSep 24, 1 PM — quietSep 24, 5 PM — quietSep 24, 9 PM — quietSep 25, 1 AM — quietSep 25, 5 AM — quietSep 25, 9 AM — quietSep 25, 1 PM — quietSep 25, 5 PM — quietSep 25, 9 PM — quietSep 26, 1 AM — quietSep 26, 5 AM — quietSep 26, 9 AM — quietSep 26, 1 PM — quietSep 26, 5 PM — quietSep 26, 9 PM — quietYesterday, 1 AM — quietYesterday, 5 AM — quietYesterday, 9 AM — quietYesterday, 1 PM — quietYesterday, 5 PM — quietYesterday, 9 PM — quietToday, 1 AM — quiet 1–5
Sep 14Sep 16Sep 18Sep 20Sep 22Sep 24Sep 26now · 2:34 AM ET
  1. 5

    Lobsters commenters challenge the essay's "singularity" framing

    Commenters argue the piece treats agents eventually mastering review, testing and deployment as inevitable, calling that assumption unproven hype, while others push back citing data on agent improvement and disputing claims about a researcher's stolen Navier-Stokes work.

    “This article seems to be pushing the singularity as inevitable, like we're all just going to be managers over a fleet of agents, pushing slop straight into production by itself.”
    — Halkcyon
    • This article seems to be pushing the singularity as inevitable, like we're all just going to be managers over a fleet of agents, pushing slop straight into production by itself. This singularity view about AI/LLM capabilities is just advertising, knowingly or not.

      Halkcyonprogramming,vibecoding13d ago21▲view on Lobsters ↗
    2 more of the top 3 · 24 posts in this stretch
    • Anecdotally, that matches my experience. Separately, I also find that a lot more of my time is spent on nailing down the requirements and design upfront before telling the agent to go and build it. And most devs on my team have to dip at least partly into project management skill set.

      carrot3055r/programming13d agoview on r/programming ↗
    • > They stole the work of a researcher who did most of the work. That's not something it's safe to assert as established fact. I think the way they handled that Navier Stokes situation was bad in a whole bunch of ways. 1. They heard a rumor that a team had made progress, so they threw tens of millions of dollars of compute at getting there first as…

      simonwprogramming,vibecoding13d ago10▲view on Lobsters ↗
    all of them →
  2. 4

    Critic dismisses the essay as "slop" on Mastodon

    Mastodon user tante posts a dismissive content-warning style reaction to the piece, rejecting its framing outright.

    “Content warning: Source is slop post…”
    — tante@tldr.nettime.org
    • The perspective of things here is interesting. I’ve always identified as someone that wants to use my skills (usually computers, maths and physics) to solve people problems. Walking into a car parts factory and delivering software they call “good” sounds almost ideal - and whether I write the code, or some juniors, or Claude, is kinda incidental…

      andyferrisprogramming,vibecoding13d ago3▲view on Lobsters ↗
    1 more of the top 2 · 2 posts in this stretch
    • tante@tldr.nettime.org

      Content warning: Source is slop post https:// seldo.com/posts/we-are-all-pro duct-engineers-now/

      tante@tldr.nettime.orgMastodon13d agoview on Mastodon ↗
    all of them →
  3. 3

    Post lands on Lobsters and draws a large comment thread

    The essay is submitted to Lobsters, where it quickly accumulates 19 comments debating its central claims about agents and the future of programming.

  4. 2

    Essay surfaces on Hacker News

    The post is submitted to Hacker News, beginning its spread beyond seldo's own audience.

  5. 1

    Seldo publishes essay forecasting AI's decade ahead for coders

    Seldo posts "We are all Product Engineers now," arguing agents will eventually eat the whole software development lifecycle while software demand stays effectively infinite, so developers won't disappear but their jobs will look unrecognizable.

    “It's good news, but not for everybody.”
    — seldo
    • seldo@alpaca.gold

      For the last 2 years I have been tracking a generational change in the nature of software development, and I think I've finally decided where all of this turmoil is going to end up. It's good news, but not for everybody. https:// seldo.com/posts/we-are-all-pro duct-engineers-now/

      seldo@alpaca.goldMastodon14d agoview on Mastodon ↗

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

Still unanswered
  • Will agents actually reach parity on code review, testing, debugging and deployment, or is that a permanent limitation?
  • Is there sustainable profit behind current AI investment, or is it a speculative bubble?