[izacus]

Who's doing all the prompting for people being laid off though? How does that transition look like?

Does the middle manager which before bugged people to do the work now write a prompt and commit code and file documents themselves?

[roboboffin]

I’m not saying people will be laid off, although this is what the article is about. So, I think people will still be prompting, but if you can prompt an agent and it can happily code away, what are you supposed to be doing ? Watching it do its work ? The only option is that you will have to generate ideas of new work constantly to drive value. This is something that generally happens over time now, but as implementation becomes quicker; idea generation will have to accelerate.

[izacus]

> So, I think people will still be prompting, but if you can prompt an agent and it can happily code away, what are you supposed to be doing ? Watching it do its work ?

Well, what do managers do once they prompt junior developers? ;)

Also, "tell a prompt and wait for it to finish without intervention" is not something that happens even with magical Claud Code.

I'd really like to see some actual theory (and position, people) surfaced that can be laid off due to AI and who and how then actually runs the LLMs in the company after layoffs. I've never been in a company where new work wouldn't fill up the available developer capacity, so I'm really interested in how the new world would look like.

[roboboffin]

I just had a thought. It used to be that complex C++ systems used to take so long to compile that developers used to go and have a coffee etc. This was before distributed compiling.

Maybe it will return to that, the job will have a lot of waiting around, and “free” time.

[fragmede]

> Also, "tell a prompt and wait for it to finish without intervention" is not something that happens even with magical Claud Code.

That is how you interact with OpenAI's Codex though.