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
Ask HN: AI productivity gains – do you fire devs or build better products?
31–40 of 244 posts
Re: Ask HN: AI productivity gains – do you fire devs or build better products?
#32Earlier quoted context omitted.
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
so where are these one man products lauched in a month? not talking about toys or vibecoded crap no one uses.
Re: Ask HN: AI productivity gains – do you fire devs or build better products?
#33Ruby on Rails and its imitators blew away tons of boilerplate. Despite some hype at the time about a productivity revolution, it didn’t _really_ change that much.
> , libraries, build-tools,
Ensure what you mean by this; what bearing do our friends the magic robots have on these?
> and refactoring
Again, IntelliJ did not really cause a productivity revolution by making refactoring trivial about 20 years ago. Also, refactoring is kind of a solved problem, due to IntelliJ et al; what’s an LLM getting you there that decent deterministic tooling doesn’t?
Re: Ask HN: AI productivity gains – do you fire devs or build better products?
#34Re: Ask HN: AI productivity gains – do you fire devs or build better products?
#35Earlier quoted context omitted.
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.
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 to them all assure me that theyre all highly skilled though. Meanwhile I've been experimenting using AI for shopping and all of them so far are horrendous. Cant handle basic queries without tripping over themselves.
This is an interesting choice for a first experiment. I wouldn't personally base AI's utility for all other things on its utility for shopping.
Re: Ask HN: AI productivity gains – do you fire devs or build better products?
#36Developers are going to be more productive, just not how you think. If history is going to rhyme, then the software industry will enter into a self-serving productivity craze building all sorts of software tooling, frameworks, ralph wiggum loop variants, MCPs, etc. much like the surge in JS frameworks and variants in the past. Most of those things will not have any business value. Software devs, myself included, love…
>> Smart organizations will not just deliver better products but likely start products [...]
This is not the 90s anymore when low hanging fruit was everywhere ready to be picked. We have everything under the sun now and more.
The problem with bullshit apps is not that it took you 5 months to build. What you build now in 5 minutes it's still bullshit. Most of the remaining work is bullshit jobs. Spinning useless "features" and frameworks that nobody needs and shove them down the throat of customers that never asked for them. Now it's possible to dig holes and fill them back (do pointless work) at much improved pace thanks to AI.
Re: Ask HN: AI productivity gains – do you fire devs or build better products?
#37Re: Ask HN: AI productivity gains – do you fire devs or build better products?
#38Earlier quoted context omitted.
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 to them all assure me that theyre all highly skilled though. Meanwhile I've been experimenting using AI for shopping and all of them so far are horrendous. Cant handle basic queries without tripping over themselves.
> I've been experimenting using AI for shopping This is an interesting choice for a first experiment. I wouldn't personally base AI's utility for all other things on its utility for shopping.
Most people dont really understand coding but shopping is a far simpler task and so it's easier to see how and where it fails (i.e. with even mildly complex instructions).
Re: Ask HN: AI productivity gains – do you fire devs or build better products?
#39Earlier quoted context omitted.
> I've been experimenting using AI for shopping This is an interesting choice for a first experiment. I wouldn't personally base AI's utility for all other things on its utility for shopping.
It's not a first experiment it's experiment 50 or 60 and, a reaction to AI gaslighting. Most people dont really understand coding but shopping is a far simpler task and so it's easier to see how and where it fails (i.e. with even mildly complex instructions).
Re: Ask HN: AI productivity gains – do you fire devs or build better products?
#40I think that it's more along the lines of "do you fire people" instead of just "do you fire devs". Fewer devs means less of a need for PMs, so they can be let go as well, and maybe with the rise of AI assisted design tools, you don't need as many UX people, so you let some of them go as well.
As for building better products, I feel like that's a completely different topic than using AI for productivity gains, but only because at the end of the day you need buy in from upper management in order to build the features/redo existing features/both that will make the product better. I should also mention I'm viewing this from the position of someone who works at an established company and not a startup, so it may differ.