Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AI doesn’t reduce work, it intensifies it

simonwillison.net

Post reply on HN
Print view View original

11–20 of 329 posts

Re: AI doesn’t reduce work, it intensifies it

#11

Post by rvz »

fhd2 wrote: post #4

I feel agentic development is a time sink. Previously, I'd have an idea, sit on it for a while. In most cases, conclude it's not a good idea worth investing in. If I decided to invest, I'd think of a proper strategy to approach it. With agentic development, I have an idea, waste a few hours chasing it, then switch to other work, often abandoning the thing entirely. I still need to figure out how to deal with that, fo…

If you do not know what you want to build, how to ask the AI what you want and are unable to tell what the correct requirements are; then it becomes a waste of time and money.

More importantly, As the problem becomes more complex, it then matters more if you know where the AI falls short.

Case study: Security researchers were having a great time finding vulnerabilities and security holes in Openclaw.

The Openclaw creators had a very limited background in security even when the AI entirely built Openclaw and the authors had to collaborate with the security experts to secure the whole project.

Re: AI doesn’t reduce work, it intensifies it

#12

Post by ap99 »

singularfutur wrote: post #10

This is not a technology problem. AI intensifies work because management turns every efficiency gain into higher output quotas. The solution is labor organization, not better software.

This argument has been used against every new technology since forever.

And the initial gut reaction is to resist by organizing labor.

Companies that succumb to organized labor get locked into that speed of operating. New companies get created that adopt 'the new thing' and blow old companies away.

Repeat.

Re: AI doesn’t reduce work, it intensifies it

#13

Post by yason »

rvz wrote: post #11
fhd2 wrote: post #4

I feel agentic development is a time sink. Previously, I'd have an idea, sit on it for a while. In most cases, conclude it's not a good idea worth investing in. If I decided to invest, I'd think of a proper strategy to approach it. With agentic development, I have an idea, waste a few hours chasing it, then switch to other work, often abandoning the thing entirely. I still need to figure out how to deal with that, fo…

If you do not know what you want to build, how to ask the AI what you want and are unable to tell what the correct requirements are; then it becomes a waste of time and money. More importantly, As the problem becomes more complex, it then matters more if you know where the AI falls short. Case study: Security researchers were having a great time finding vulnerabilities and security holes in Openclaw. The Openclaw cre…

> If you do not know what you want to build

That describes the majority of cases actually worth working on as a programmer in the traditional sense of the word. You build something to begin to discover the correct requirements and to picture the real problem domain in question.

Re: AI doesn’t reduce work, it intensifies it

#14

Post by foxes »

ap99 wrote: post #12
singularfutur wrote: post #10

This is not a technology problem. AI intensifies work because management turns every efficiency gain into higher output quotas. The solution is labor organization, not better software.

This argument has been used against every new technology since forever. And the initial gut reaction is to resist by organizing labor. Companies that succumb to organized labor get locked into that speed of operating. New companies get created that adopt 'the new thing' and blow old companies away. Repeat.

Maybe society shouldnt be optimising for that.

Re: AI doesn’t reduce work, it intensifies it

#15

Post by gedy »

fhd2 wrote: post #6
bilekas wrote: post #3

> I've had conversations with people recently who are losing sleep because they're finding building yet another feature with "just one more prompt" irresistible. This is actually a really good point that I have kind of noticed when using AI for side project, so being on my own time. The allure of thinking "Oh I wonder how it will perform with this feature request if I give it this amount of info". Can't say I would p…

What kills me personally is that I'm constantly 80% there, but the remaining 20% can be just insurmountable. It's really like gambling: Just one more round and it'll be useful, OK, not quite, just one more, for hours.

And let's get real: AI companies will not be satisfied with you paying $20 or even $200 month if you can actually develop your product in a few days with their agents. They are either going to charge a lot more or string you along chasing that 20%.

Re: AI doesn’t reduce work, it intensifies it

#16

Post by Pingk »

erelong wrote: post #2

Doesn't have to be that way, it's about managers being realistic and not pushing people too far

You do it to yourself, you do, and that's why it really hurts.

> Importantly, the company did not mandate AI use (though it did offer enterprise subscriptions to commercially available AI tools). On their own initiative workers did more because AI made “doing more” feel possible, accessible, and in many cases intrinsically rewarding.

Re: AI doesn’t reduce work, it intensifies it

#17

Post by taosx »

mrtksn wrote: post #8

Computer languages were the lathe for shaping the machines to make them do whatever we want, AI is a CNC. Another abstraction layer for making machines do whatever we want them to do.

I don't disagree with the concept of AI being another abstraction layer (maybe) but I feel that's an insult to a CNC machine which is a very precise and accurate tool.

Re: AI doesn’t reduce work, it intensifies it

#18

Post by embedding-shape »

yason wrote: post #13
rvz wrote: post #11

Earlier quoted context omitted.

If you do not know what you want to build, how to ask the AI what you want and are unable to tell what the correct requirements are; then it becomes a waste of time and money. More importantly, As the problem becomes more complex, it then matters more if you know where the AI falls short. Case study: Security researchers were having a great time finding vulnerabilities and security holes in Openclaw. The Openclaw cre…

> If you do not know what you want to build That describes the majority of cases actually worth working on as a programmer in the traditional sense of the word. You build something to begin to discover the correct requirements and to picture the real problem domain in question.

> You build something to begin to discover the correct requirements and to picture the real problem domain in question.

That's one way, another way is to keep the idea in your head (both actively and "in the background) for days/weeks, and then eventually you sit down and write a document, and you'll get 99% of the requirements down perfectly. Then implementation can start.

Personally I prefer this hammock-style development and to me it seems better at building software that makes sense and solves real problems. Meanwhile "build something to discover" usually is best when you're working with people who need to be able to see something to believe there is progress, but the results are often worse and less well-thought out.

Re: AI doesn’t reduce work, it intensifies it

#19

Post by localhoster »

TBH, I have found AI addictive, you use it for the first time, and its incredible. You get a nice kick of dopamine. This kick of dopamine, is decreasing with every win you get. What once felt incredible, is just another prompt today.

Those things don't excite you any more. Plus, the fact that you no longer exercise your brain at work any more. Plus, the constant feeling of FOMO.

It deflates you, faster.

Re: AI doesn’t reduce work, it intensifies it

#20

Post by wiseowise »

> I've had conversations with people recently who are losing sleep because they're finding building yet another feature with "just one more prompt" irresistible.

Literal work junkies.

And what’s the point? If you’re working on your own project then “just one more feature, bro” isn’t going to make next Minecraft/Photopea/Stardew Valley/name your one man wonder. If you’re working for someone, then you’re a double fool, because you’re doing work of two people for the pay of one.

Post reply on HN