7 pointsby user21321413 hours ago9 comments
  • san_tekartan hour ago
    One thing that seems overly definitive is the AI cost premise. If the bills are that massive, they are either letting autonomous agents run wild in uncontrolled token-burning loops, or they are conflating developer tooling with customer-facing API costs (COGS) and model training. If it's the former, the fix is internal developer education and better guardrails, not layoffs.

    A premium developer setup—like Claude Code Max combined with Gemini Pro—costs under $300-$400 per developer a month. Compared to a standard developer's $10k+/mo payroll, that's a negligible rounding error (around 1.5% to 3%). The argument that companies are forced to lay off developers to afford their tooling seems highly exaggerated at this point.

  • 3 hours ago
    undefined
  • codingdave3 hours ago
    > but not many will want to work at a tech company today that doesn’t provide top tier AI tooling,

    wat. No. There are plenty of devs who hate how AI is changing the work, and would be thrilled to go back to the old ways. I am seeing so many arguments that amount to "We all have to use AI because... we all have to use AI." People start with the assumption that AI will take over and then use that to work backwards and prove that we all must use it for everything.

    If anything, we're starting to see the opposite. I'm hearing more and more discussions from my clients that the increasing cost is not sustainable, and the increase in problems is not the result they were hoping for.

    There is a strong argument that such clients aren't using agentic processes correctly. But at the same time, when I show them how to improve such processes, the bills go even higher.

    We have not yet landed on the tools and processes that will make AI take over all work. Nor have we proven that such a scenario is inevitable.

  • Our_Benefactors2 hours ago
    This is the best way I can explain why ai-driven layoffs can be logical.

    Take a baseline as 5 devs costs 5 salary units and produces 5 output units.

    AI does something like “for 1.25 salary units you get 1.5 output units” so it’s costlier on a per-dev basis, but you get 6 output units for 5 salary units, but only have the budget for 4 devs with AI. You would be a failing leader to argue for 5 output units over 6. That’s essentially the calculus that’s going on today. How much more output is gained from spending on AI compared to hiring more devs. Nobody has figured out how to measure it yet, but it’s clear that spending more on individual devs is the path to increased productivity.

  • damnitbuilds3 hours ago
    "You’re firing people just to make more profit by not having to pay those extra devs"

    You seem not to understand how companies work.

  • dexarude3 hours ago
    could be
  • Leena-ch32 minutes ago
    [flagged]
  • michaelmjh2 hours ago
    [flagged]
  • bigbigeggss2 hours ago
    [dead]