AI isn't killing jobs, it's 'unbundling' them into lower-paid chunks

egonschiele

> The human is left doing whatever the machine can't, often a narrower slice of the original role I haven't seen anyone talk about AI and its impact on flow yet. It's pretty easy for me to achieve a flow state while coding without AI, but with AI, I'm not so sure. I spend my time managing multiple Claude instances as they work on different tasks, and there's no time to go really deep into anything. Flow was such a productivity boost for me. Even though Claude definitely helps me finish tasks quicker, I've started wondering how much quicker it actually is, vs getting into flow.

danans

> In strong-bundle occupations… AI improves performance inside the job, but does not remove the human from the bundle," the authors argue. At least in software engineering, AI can't replace the accountability that only humans can provide, but it multiplies the surface area that a human is accountable for, driving up the work demands on worker in one dimension while it lowers the demand for actual coding. On balance, it's more work down with far fewer people. > It also squares with what we're seeing so far. AI is reshaping jobs, not wiping them out. Tasks move around, productivity may go up, yet employment and hours haven't shifted much – at least yet. In many cases, the bundle is still holding. AI will supercharge the decades-old trend of productivity growth dramatically outpacing both employment and compensation, as the returns go primarily to the owners of capital. The result: a lack of job growth while productivity still rises, and also stagnant wages as workers lose the labor market leverage.

h4kunamata

OP is clearly living in a paralell world. We have managers using chatbot to write code instead of engineers themselves. Company after company using AI for everything over humans. If you say that AI is not killing job in 2026, you are delusional.

uduni

How is this different from previous layers of abstraction? React/JS dev don't have to think about memory management or a million other things that C++ application devs did. Instead that cognitive load is unbundled onto the framework maintainers, and frontend devs can be much more productive. Obviously react/js didn't cause job apocalypse... Quite the opposite. It's just another abstraction layer making it possible to build a full application with less text. Prompts are the same pattern again IMO

4er_transform

If you’re wondering what is left when you have a swarm of generally intelligent agents working on your behalf and can do every task as well as a human, we already have the answer. That is the life of a CEO. Humans are left deciding the direction, choosing what matters and what to spend attention on, and making judgement calls on the edge cases. In the future, everyone is a CEO. How many CEOs are there though in that future? Probably not 8 billion

agent_anuj

been in enterprise tech for 20 years and what I see is what I will call unbundling. its more like seniors are now doing work of 5 juniors because AI does the grunt work. so companies just dont hire juniors anymore. but the senior guy doesnt get paid 5x, maybe 1.2x if lucky and expected to output 5x. I myself have gone back to hands on coding in last 6 months along with managing the team. so now I am doing both developer and manager role. company loves it obviously but I am not getting paid more to do both and juniors in my team are under severe pressure to show thier worth. thats not unbundling thats just squeezing people. And companies will continue to do it.

with

Just further proof that context is the real moat, not intelligence. All the models are already converging to be equally intelligent and that will only continue. GPT 5.4 / Opus 4.6 are the first two models I’ve used where I’m like, yeah, with the right spec/context they can pretty much do anything. The “bundle” or “context” is the value.

nurettin

I've been on the receiving end of development. You waited months for a POC. You ripped your hair out as the developer responsible for adding a backend to batch move stock wanted to chat to you about his wife's bird pictures during lunch while weeks into "the big feature" (literally an upsert). I'm just glad that the tea party of corporate programming is over. Whatever comes next, it cannot possibly be worse.