If AI brings 90% productivity gains, do you fire devs or build better products?

i was rolling my eyes at the hype, but reading about this is totally different from experiencing it. if you have any old repos out there - try it, you might actually be amazed.

i'm not sure i buy the long-term "*90% productivity*" claims for complex, legacy enterprise systems, but for the boilerplate, libraries, build-tools, and refactoring? the gain is gigantic. all the time-consuming, nerve-wrecking stuff is mostly taken care of.

you start off checking every diff like a hawk, expecting it to break things, but honestly, soon you see it's not necessary most of the time. you just keep your IDE open and feed the "analyze code" output back into it. in java, telling it to "add checkstyle, run mvn verify and repair" works well enough that you can actually go grab a coffee instead of fighting linter warnings.

the theory is that what remains is just the logic and ideas. we'll see how that holds up when the architecture gets genuinely tangled. but for now, letting it branch off, create boilerplate, and write a simple test while you just iterate on the spec works shockingly well. you only write source code when it's too annoying to write down the spec in plain english.

it raises the real question: if your competitor Y just fired 90% of their developers to save a buck, would you blindly follow suit? or would you keep your team, use this massive leverage, and just *dwarf* Y with a vastly better product?

14 points | by Bleiglanz 3 hours ago

10 comments

  • lordkrandel 2 hours ago
    Why do people keep ralking about AI as it actually worked? I still don't see ANY proof that it doesn't generate a total unmaintainable unsecure mess, that since you didn't develop, you don't know how to fix. Like running a F1 Ferrari on a countryside road: useless and dangerous
    • giantg2 15 minutes ago
      I see more value on the business side than the tech side. Ask the AI to transcribe images, write an email, parse some excel data, create a prototype, etc. Some of which you might have hired a tech resource to write a script for.

      On the tech side I see it saving some time with stuff like mock data creation, writing boiler plate, etc. You still have to review it like it's a junior. You still have to think about the requirements and design to provide a detailed understanding to them (AI or junior).

      I don't think either of these will provide 90% productivity gains. Maybe 25-50% depending on the job.

    • tyleo 52 minutes ago
      Because it's working for a lot of people. There are people getting value from these products right now. I'm getting value myself and I know several other folks at work who are getting value.

      I'm not sure what your circumstances are but even if it's not true for you, it's true for many other people.

      • pydry 3 minutes ago
        It's interesting that the people IRL I encounter who "get the most value" tend to be the devs who couldnt distinguish well written code from slop in the first place.

        People online with identical views they all assure me that theyre all highly skilled.

    • thefounder 33 minutes ago
      You can launch a new product in one month instead of 12 months. I think this works best for startups where the risk tolerance is high but works less than ideal for companies such Amazon where system failure has high costs
      • dominotw 25 minutes ago
        so where are these one man products lauched in a month?

        not talking about toys or vibecoded crap no one uses.

        • fragmede 6 minutes ago
          Aside from the things people have launched that don't count because I'm right, where are the things that have been launched?
    • Kim_Bruning 46 minutes ago
      Consider it this way as a reasoning step: We've invented a cross compiler that can handle the natural languages too. That's definitely useful; but it's still GIGO so you still need your brain.
    • the_real_cher 1 hour ago
      Yeah its great but as the OP said you have to watch every P.R. like a hawk
  • jaen 20 minutes ago
    That's assuming every developer can get the same AI efficiency boost and contribute meaningfully to any feature, which is unfortunately not really the case.

    Seniors can adjust, but eg. junior frontend-only devs might be doomed in both situations, as they might not be able to contribute enough to business-critical features to justify their costs and most frontend-related tasks will be taken over by the "10x" seniors.

  • giantg2 25 minutes ago
    I feel like the ideas have always been the tough part. Finding novel ideas with a good return is extremely tough.
  • aurareturn 3 hours ago
    In certain industries, increasing productivity by 90% does not mean 90% increase in profit. This is because growth depends on market TAM and growth rate.

    Another way of increasing profit is to simply reduce your headcount by 90% while keeping the same profit.*

    Hence, I think some companies will keep downsizing. Some companies will hire. It depends a lot.

    *Assuming 90% productivity increase.

    • muzani 20 minutes ago
      In companies like the oil industry, doubling productivity would mean reducing the expected life span. Costs tend to catch up with profits, especially due to taxes. Layoffs happen inevitably.

      Is it the same with tech? Facebook has 3 billion monthly active users. No amount of tech will bring that up to 6 billion. If you were to double the amount of time someone spends on Facebook, or double the ads they see or double the click through rate, what does that really mean?

  • conartist6 31 minutes ago
    Gotta fire everyone, or else "too many cooks" will mean that even those temporary productivity gains go up in smoke.

    Remember sometimes the most productive thing to have is not money or people but time with your ideas.

    • conartist6 27 minutes ago
      What's so sad to see is people excited about making something selling away the time they would have with their ideas. They're paying money to not use their brain to contemplate the thing they should be the foremost expert in the world on, and they're excited to be paying more and more for each modicum of ignorance and mediocrity dispensed.
  • iExploder 1 hour ago
    yes you fire if you are a burned out company that only needs to maintain its product and slowly die...

    you hire more if you are growth and have new ideas just never had the chance to implement them as they were not practical of feasible at that level of tech (non-assisted humans clicking code and taking sick leaves)

  • _wire_ 3 hours ago
    "I just got my third coffee and I'm feeling really good about the quality of this code. I don't even bother to look at it. Keeps my tests simple to not test at all. You know, 'in theory'. Of course when the architecture gets genuinely tangled... Just keep your IDE open so the code knows where to go. Whoa, too much caffeine, super sleepy..."

    Terafab is suddenly making so much sense!

  • Remi_Etien 2 hours ago
    [dead]
  • cochinescu 1 hour ago
    [dead]