In some cases, workers are also being asked to automate the parts of their jobs they enjoy most, Hinds said on the podcast, pointing to customer-service employees who enjoy building relationships but are increasingly expected to supervise AI agents instead.
"That's what gives you joy and meaning at work," she said. "That is very dangerous."
What's a 20% productivity gain if I constantly feel deflated by work that used to energize me? That's going to give back the productivity gain and more, while also decreasing my quality of life.
He said, "Almost half of what we do is not that valuable to our customers, but it's valuable to him, and her, and him", pointing through the conference-room window at my fellow programmers, "and that's why we do it. If we only did things that were very valuable to our customers, we wouldn't have nearly as many good engineers on the team as we do."
This quote makes it seem like the work is self-indulgent, and I have seen that happen sometimes, but it's not half of what we do.
Even everyone earnestly trying to identify the feature that IS IMPORTANT to clients and will actually be used and appreciated frequently is something of a crap shoot.
You come to a point where you realize that you're not doing anything that creative, or nothing you haven't done hundreds of times before, maybe every few years you switch to whatever new tech stack has gotten popular, but it's fundamentally all the same. And you start to realize that everything you do has a lifespan of a few years, and then you (or probably someone else) will re-do it.
As retirement starts feeling like it is something that will happen sooner than later, you look back and see that almost nothing you've built is still in use, or will be for very long after you're gone.
I hope to retire in about two years. At that point, I plan to not be using any technology or computers in my life for a while, or as little as possible. Maybe at some point I'll rediscover some of the fun I used to have writing programs for myself, but I suspect I'll need a long break before that happens.
But honestly I've stopped being excited to type out code in my personal projects anymore either. I've become much more excited by what I can accomplish on my own in a small number of hours squeezed between work and family. I still experience this as a loss, but I'm no longer so sad about it, and moreso feel invigorated by the possibilities and opportunities that have been opened up.
A way that I have come to think about this is: I used to always be curious about the product management role. How exciting to come up with ideas and validate them with users. But I always demurred because it would be so frustrating to have to rely on other people to bring those ideas to fruition! On balance, I always preferred being the one executing ideas to being the one generating and validating them. But now I can properly do both things! (In my hobby time, that is, at work we still have this idea/execution split, at least for the time being.)
Then they announced that they removed the limit/making further request just cost extra for them. That's when I started using it as I did for my personal projects I pay subscriptions for...
Then Copilot increased their pricing. Announced in April I think? But took effect this month. This Monday they announced that the limits are back in effect. So I guess I'll be going back to hand coding next week, as my tokens are about to run out ಥ ‿ ಥ
Corporate is always so silly. I mean I know how it happens: everyone just wants to get their bonus, so different management roles try to coerce the employees to do whatever best serves their bottomline - rarely related to whatever is good for the corporation... But it's always silly to live through it.
Programming was one of the ones which was, because there were fewer programmers than openings. Now that's flipping, thus naturally, the enjoyment is going to be sucked out of it.
But SHOULD we? With great power comes great responsibility - and I'm getting the impression we're (quickly) building a world that isn't very fun to live in. We technically have a choice here - DO we want bots writing our prose and responding to our customer service inquiries?
OTOH, I think we absolutely SHOULD automate necessary "drudgery" type work wherever we can, but we're going to need a radical reconceptualization of how we distribute the spoils of economic productivity as a result. Unfortunately, I think the type of reconceptualization we'd need would entail a complete overhaul of many long-established and deeply-internalized concepts (rights and duties of ownership of intellectual and private property, decoupling of identity and occupation, etc.), and from everything I've seen, that will be a long and painful process assuming it's even achievable. (Especially in the US, where decades of pro-business messaging has yielded a culture that equates income-earning ability/entrepreneurial success with individual human worth. I really struggle to imagine a path toward unwinding that, but there's little chance it'll be a smooth ride.)
It sucks for the employees, otoh it might be the only way we're going to beat Baumol's Cost Disease.
In the past few decades productivity has exploded, but service employees have largely failed to increase productivity in any way because it's harder to automate these tasks.
It's the reason the costs of things like education and healthcare are downright extortionate, the reason you're paying back your college well into your fifties, the reason you don't call an ambulance for someone in the US because you don't want to ruin their life financially.
We may have to trade the personal fulfillment in these jobs for the broader affordable access to these services.
You might wanna think again on that line of reasoning, because plenty of other countries have the same dynamics with respect to service employees, but they don't suffer the very US-only problem of ridiculous education and healthcare costs where calling an ambulance can ruin someones life.
Weird. I thought it was the fact that you have a cohort of people who are grossly overpaid to represent people who do none of the work yet expect an ever-increasing amount of value created by the work to be shifted to them every 90 days, no matter what, forever.
> We may have to trade the personal fulfillment in these jobs for the broader affordable access to these services.
Then you'll run into two problems:
1) no one will want to do necessary jobs without increased compensation, which is at the root of your analysis of "Baumol's Cost Disease"
2) at least in the US, you'll have a bunch of increasingly miserable people living in a society that gives them less and less to lose while increasing the availability of things that allow them to take out their frustrations upon themselves (substances) or others (weapons)
I think it is more important than ever to manage your wealth in a way that sustains you from capital alone in a world where employment gets progressively more toxic.
The way to achieve it is buying maintenance efficient and cheap car, make renovations smart, make good choices all around to minimise expenses. Operate your life like a corporation. First, cut the expenditures.
For me the ability to do whatever I am interested in at the moment, is worth almost any sacrifice.
Then I can seek one time contracts or short time jobs that fulfil my mental needs.
My monthly expenses are no more than 5000 dollars and mostly consistently less than that.
Which is okay because the money spending doesn’t bring me any joy nowadays. The money isn’t what gives me happiness. Only other people can provide that and activities that are dirt cheap usually, like reading or broadly understood hacking
Consumption is a short lived and deceptive joy that causes more guilt than whatever dopamine it is worth really. Governments hate people like me which means I must be doing something right.
Both are areas where costs are going up at a rate which is much higher than official inflation rates, and comp increases often don't even match inflation!
So the need for working till you're forced to give up still remains.
I am having some success in working to acquire a taste for different parts of the work. But I suspect that this won't be an option for most people.
Whatever productivity gains models are giving us is being eaten away by other factors.
but did we increase our EBITDA for the quarter?
Where did the 20% number come from? I’d argue it’s way more than that (or variable, i.e. dependent on who’s using it/how it’s being used/what it’s being used on).
Having said that, the number, to me, doesn’t even matter. You could replace that with 200%, and it’d be just as true.
This has been the story of humanity since the industrial revolution.
Except the intern is trapped inside an iron lung and must communicate entirely by text. And also has zero real creativity or self-motivation.
The real problem is the amount of value that gets left on the table.
Also, mental health is just as much a part of health and well-being as the physical.
I think it's called 'capitalism'
Now they get to fill out excel sheets, babysit people and sit in planning meetings.
Unfortunately though, what does that matter? Your employer does not care how do you feel. You are paid to bring them benefits, they aren't running a charity. If you do feel down, that is your issue and you shouldn't let that influence how you work.
Just to be clear, I don't like that either. But it is what it is.
It's not defiance, it's reality: if you drag down my motivation, that's going to drag down my productivity. I don't really have much active control over that.
Generally, I spend anywhere between 15 mins and an hour setting things up (depending on how well the project is set up for AI work), and then set the agent going, coming back in a half-hour to an hour to check its progress. Generally, the tooling keeps it honest (for golang, forbidigo is AWESOME). 80% of the questions the agent asks me require a lot of thought. 20% of what it does needs correction.
The other thing to remember with LLMs is that they are NOT human, and won't react in a human way. So you'll see strikes of "brilliance" followed by the absolutely bizarre. But good guardrails keep that to a minimum.
AI should be assisting us, instead it's doing the job and it's us being an assistant to it. This is a monumental shift that people seem to be missing in how knowledge working is changing and it's going beyond mere coding.
Guardrails, prompts, whatever, it's us helping it doing the job, not the other way around.
Opus 4.6 was the last genuinely good assistant LLM, but since then it's quite clear that the training/reinforcement is focused "given prompt -> do task" so it's behavior is more and more about doing it itself, not helping you. If you try to use it as an assistant it just sucks and is perma wired into finding the solution. Many times I want it to help me investigate, and his answer will still be focused on the fix, not answering my questions.
4.7 first, 4.8 later and fable are absolute disasters as assistants.
Fable in particular is so "intelligent" that it will push with very strong and intelligent takes even if it is completely wrong.
I have never disliked our job more.
To me, this feels in many ways like a technical manager or team lead's job, where I guide the process along using my knowledge and experience, and then let the agent fill in the rest (to the best of its ability).
The agent can't really learn from its mistakes (at least, not without consuming precious context), so I apply a blameless postmortem process, updating the guardrails whenever it goes astray in the same way more than once.
And really, I'd rather be contemplating the more difficult and interesting questions of architecture, environment, ergonomics and market fit, so it suits me fine.
If you're a manager and you ask a report to do something and they come back with a question, does that mean you're now their assistant?
I give agents the tasks, I answer their questions, I make choices about the tradeoffs in their plan, I supervise their implementation, I review their output, I have them walk me through things. In what way is this not delegating to them and managing their work, just like a more junior employee?
Consider what is happening in most construction sites. The heavy work is absolutely from the technology on site. But without people there to oversee it and keep it working, it would fail.
And that is almost certainly true at any industrial site. Indeed, look up videos of high tech looms. A large portion of the technology added to them are so that the operators can locate the fault and fix it.
Are you getting LLMsplained? :)
Which is why (well, part of why) I think the long-term trend will be towards self-hosting models. Right now the frontier models are far enough ahead of the self-hosted ones that there are lots of people willing to pay by the token to rent someone else's model, because they get more value for money from that than from self-hosting models.
But the frontier companies won't be able to keep up their current levels of expenditure forever. At some point the investors are going to say "Hey, so, um, when am I going to see some return on my investment?" and then the current subsidized subscriptions (including the one my employer uses) are going to go away, much like what happened with Copilot this month.
And then the locally-hosted models are going to suddenly look like a more attractive picture. Because where you might have been willing to spend $100/month/employee to rent time on models in someone else's data center, you might suddenly balk at spending $500/month/employee. You might say "Hey, you know what? A $50,000 up-front capital investment is only, what, one month's worth of subscriptions for our 100 employees? Yeah, okay, I'll approve the hardware purchase. Get that self-hosted model set up and then we'll cancel the subscription and switch over."
Not everyone is going to do that. But once the locally-hosted models are good enough, the first few people who do so and report success are going to start a snowball effect. And it will likely be driven by money first, but it will also have the effect, that people will slowly discover, of meaning that you can better predict the model you're using. It will continue to work the same way next year that it is working this year; or if it doesn't, it's because you chose to install the new version.
And when that happens (I'm saying "when", not "if" because although it might take some time, I think it's inevitable in the long run), the frontier-model rental companies are going to struggle to stay afloat. Except for the ones who saw this coming and transitioned to a non-subscription income source somehow (maybe by selling licenses to self-host their frontier models for $$BIGNUM), or who have some other revenue stream besides renting out models.
> 80% of the questions the agent asks me require a lot of thought. 20% of what it does needs correction.
I've found even the permissions questions give me veto power over fruitless lines of exploration, especially in planning mode. For instance, it wants to use tools I don't have installed to access information that I have made available elsewhere? I get a chance to override this decision by declining the permissions check and redirecting it. Feels tedious, but helps me understand what information sources are influencing it. I head off a lot of bugs this way.
I think the yoloist counter-argument is "So what? Let it. It'll take longer that way and consume more tokens, but you can work on something else in parallel instead of being hooked in to this one session".
Once that's set up, I spend time laying out the planning for whatever feature or fix is being worked on. For fixes the agent is pretty quick and usually needs little guidance. For new features it's best to have more of a hand on the tiller.
Like others said, the frustration is when it gets something so wrong you just think "wow, how'd you mess that up?" but when it gets it right its kind of nice. I also dont like that I basically tell Claude what to do, and then either go to busy work or waste time on the internet.
It may be fun to look at inputs and outputs, but it's not hackable and trying to map one into the other is more like astrology than a science.
I suppose it's the same as asking someone else to take care of a feature and hoping they understand what you have in mind. The difference is that there's a lot of context that's shared between you and a human developer that is simply absent with AI.
as a boss (or researcher) i'm going to measure productivity based on amount of output per hour that i'm paying you; as a workers, i'm going to measure productivity based on amount of output relative to the amount of effort i'm putting in.
so what may be happening is that bosses see that output is at 80% (productivity down!) but workers see that they can give that 80% output with 40% effort (productivity up!).
Early on in my days as a sysadmin, I automated a ton of my role when the rest of the team was still doing ClickOps. The reward for doing so was more work and expectations without the additional pay increase to justify my new found productivity. That happens all over the workforce, and so people will just keep it to themselves. I learned my lesson at that first job real fast that if I'm able to have the same, or greater output, for half the time, I keep that to myself so I can use the automation to free up my own time instead of have it filled by the company.
I wonder how much of that is happening now with AI in non-technical roles.
If an initiative produces only 80% of the previous results and you’re paying large token bills on top of the same wages, the AI is going to get cut off.
> i've seen a number of articles claiming things like "devs self report they'er +x% more productive with AI, but actually they're -y% LESS efficient!".
Are you thinking of the old METR evals? Their more recent evals showed an actual performance improvement.
The old report is still circulated as bait for AI skeptics.
[1]: https://metr.org/blog/2025-07-10-early-2025-ai-experienced-o...
[2]: https://metr.org/blog/2026-02-24-uplift-update/#wider-adopti...
So why is it that the bosses are the ones that are so enthusiastic about adoption?
https://www.faros.ai/blog/ai-acceleration-whiplash-takeaways
Faros would tell you shops are shipping 16% more PRs with heavy AI use.
https://unessays.substack.com/p/talk-is-cheap
I think that's wrong because it doesn't adequately account for the quality and rework their data show.
I just can't imagine tanking my trust with my coworkers by doing something like that.
That's what I wonder about, what happens to all those folks.
Managers will be sure to tell you how much they respect you. Ask them if they respect the work and you'll get a blank stare.
If you spend countless hours at work, and you partially define yourself by your work, and you realise you are easily replaceable then I cannot imagine this comes without mass social malaise that manifests itself elsewhere.
When you know you're essentially babysitting the workhorse to ensure it doesn't go off the rails, I can't see job satisfaction, and the social consequences of such, increasing.
I don't have data to support this (other than, I guess, my LinkedIn feed), but my impression is that the management class is pushing AI _way_ harder than the worker / craftsperson class.
And if that's true, I think it's perhaps because it's something they understand: you tell AI to do something, and (with varying degrees of success and less complaining)... it does that thing.
To the extent that I've seen craftspeople adopt AI, it's been because they recognize its usefulness as a tool to further their craft. I don't meet many craftspeople that enjoy watching any[one|thing] do their work for them.
LLM worker > Harness, Agents w/ skills > Human oversight/input
This is similar in structure to many teams I work with, something like:
Dev/SE/etc > PO > Manager/Director
Or whatever your current org structure relates. The LLM worker and Harness/Agents compact down to one human layer.
Now with MOE LLMs, the LLM layer is breaking into like:
LLM worker > LLM router > Harness, Agents w/ skills > Human oversight/input
Does that mean the Human element can be condensed to a single Manager with the right skills? A Director above them? Is the VP above them directing the agents?
Is this another variation of Conway's law, where orgs design systems that copy their own communication structure? Seems like that is how my Manager/Director approach it. Then again, they are making slide shows and obviously AI assisted reports, not something that needs to be stable and responsive for the entire product lifetime.
But to your point, the manager sees it as a structure to manage to increase productivity. The craftsman sees it as a tool to further their craft. Each is driven by a different methodology and use case. Can that mesh unless specifically directed to throw AI at no joy work?
Welcome comrade. https://en.wikipedia.org/wiki/Marx%27s_theory_of_alienation
I agree entirely. Even in an idealistic fully egalitarian post-scarcity society, to truly be happy I think most people would need to do work that they can feel a sense of accomplishment about. The problem is that work at most jobs is increasingly just toil. Any possibility to scrape some tiny flakes of satisfaction out of the toil gets removed, often for no good reason.
That's easier with things like farming, but it's totally possible with highly-automated jobs; you just can't have managers treating us like we're machines.
This is something that I don't see discussed a lot in these conversations, but its true for a ton of folks.
I didn't end up with a career in tech because I wanted to tell a bot to do the fun part of my job for me, leaving me only with the boring tedious parts. I didn't sign up to be a full time code reviewer, and I certainly never wanted to be a manager, yet alone a manager of bots.
It also can't help but spark feelings of "Why am I getting paid 6 figures for this??" and that makes me nervous for the future.
I imagine the engineers and assemblers in factories pre-assembly line felt the same when things started getting automated there. There's an element of craftsmanship that gets taken away as the product moves from being artisanal, hand crafted to mass produced.
I wonder if its too late for me to pivot to hardware
But those times when I had to drop down into a repl and play around with the output of a method. Or try different ways of doing what anyone else would think is boring, like array manipulation - that's a lot of what I actually LIKE to do.
A big part of me just hopes I can hang in there for another... decade, or two. Then I can retire! Maybe.
It's actually kinda pleasant, especially when I consider all the tickets I'm not excited about doing. It's prob worth focusing on that aspect of it.
If I was valued at 1 trillion dollars, and I was in the hole enough to sink a couple small countries' GDP, maybe I would slowly start to optimize to maximize token usage.
I want to sell tokens, how do I sell more tokens? Not by doing the same work in less tokens, that's for sure.
This is like if you pay me by the hour and then excitedly tell me that you keep paying 10k a month and it's great. I will most certainly not work faster, in this hypothetical, if you tell me you love spending money because it gives you a dopamine rush. I would probably spend a couple more hours REALLY thinking about the task, maybe writing some docs nobody will read, maybe considering multiple options, doing benchmarks, doing research, and then later maybe ill do the actual task as well.
Im not saying these AI companies are scamming us, but the incentives are there and extremely clear. The only thing currently holding it back is that there is some vague kind of competition.
The ability to assess the user's goal and tune the inference accordingly is there. So, what methods are there to tell if a provider has their thumb on the scale?
Plodding along a longer path to the same goal would burn more tokens without necessarily a decrease in solution quality. Maybe a few more docs.
The best I can say is that genAI is a self reported a 20% efficiency boost, and for a very (very) small group of people, it’s maybe a 2-3x boost. (And if you are at a frontier lab, you go fly into the big bucket of exceptions)
At this point, for most use cases, AI productivity is either the equivalent of giving people 3D printers, and seeing little benefit, or signing up for an outsourcing service, just without the development of human capital anywhere.
Agreed. I think one of the hardest things about it is that productivity != value. You can push all the code you want, but if it's not driving revenue up or cost down, it doesn't matter economically.
Here is the best data I've been able to find. An observational study of 4000 teams over 2 years across many different organizations. Data gathered from their task management, version control, and CI/CD tooling. Critically - this is not survey data. It's much more direct measurement.
https://www.faros.ai/blog/ai-acceleration-whiplash-takeaways
Faros argues that teams are seeing about a 16% throughput improvement (PR merge rate) with heavy AI use.
I argue here that their data actually indicates negative absolute impact on throughput.
6 hours of debugging and docs reading is not equal to 6 hours of prompt fiddling. The return of value beyond the few fixes applied will be almost nil from the fiddling.
HN posts seem to go from very supportive to very critical of AI with very few articles striking a balance.
Was there a time or technology phase in the past (I'm thinking perhaps when everyone was going over to GraphQL just because of the hype) that you recall being similar to this? If so, how did you maintain curiosity without feeling yourself go through the extremes of "This is the worst / best thing to ever happen"?
So for my work, it's made me much better at my job. Much faster and more accurate.
I can write a simple query before Claude finishes reading, querying the semantic layer, checking my files, then writes a query that I have to approve, reads the results, hides them (ctrl+o usually works), and gives me a summary.
We’ve reached this inflection point where it’s faster for me to do most tasks again.
I’m sure fast mode costing more money plays a role.
Welcome to the factory!
The problem is, we haven't had the debate on a societal level if we want to go the star trek route (aka, we give our darn best to automate everything so that humans have the time to do whatever they want) or the realcommunism route (we ward off automation so that we have jobs for people).
The result of that debate not having been made is the third possible outcome - rabid capitalism automates everything as soon as it is profitable and lays off the humans, focusing on getting higher margins out of less people if need be; the best example for that IMHO is Disneyland or Vegas going on ridiculous nickel-and-diming tours. In the end however, there will be no one left any more who has employment and we'll be in for quite the riots.
I’ve been told before.
In the last century I enjoyed crafting my own 'libraries' of functions that I could then use on the projects I worked on. As time went on, there was less and less of a point doing that as the odds rose near to 100% that there was 'a library for that' thing I was working on, so I was encouraged/forced to download it and use it.
It solved problems and was quicker than writing bespoke code (and libraries were hardly a new idea), so the logic was hard to deny, but I enjoyed my job less over time. Now I've risen up the ranks and now code mostly for fun (yes, I use AI to write functions for me) I look at what it must be like to enter the industry and think it all looks very different to how it did when I started.
You could argue that AI has done this much faster than it did in my early career, so people have less of the 'boiling frog' experience I had, and more of a 'sudden shock' to the system.
It's sad, but I've been doing this to other industries all my career, so I can hardly complain.
But now it's happening at the company level: "We're going to add a chatbot to increase productivity! Now MCP tools! Then agentic workflows! We’ll add skills, and now productivity will go up! Maybe loops will do it?"
(There's a reason why I call it the MBA's stone. It transmutes all knowledge work into a problem of management.)
I've used it plenty, more recently than ever before, but I'm coming more and more to the conclusion I don't want anything to do with it.
Botsitting is low-skilled. Low-mental reward work will become low-financial reward work before long.
I was initially worried that I had to keep up, learn the new tools or get left behind. But I'm beginning to see it as an entirely different domain of work, and one I'm fine not doing.
I think I'm best off preserving my skills and autonomy, rather than fighting with an agent and fretting about tokens for the foreseeable. I've no desire to be a botsitter.
Worst case scenario, this really is the future, and I become unemployable in tech: I've done other sorts of work in the past, things I'm happy returning to if this is the future.
I've a hunch that's still going to be a while off. I hope so anyway.
the wild thing is, i liked my job 3 years ago. i liked the satisfaction of creating for sales. they could be annoying, but it was minor normal (human) corporate squabbles. now, when they're explicitly bragging about getting rid of designers and treating us as sub-human, it's creating resentment and misery. personally job satisfaction sharply decreased in the last 6 months let alone the last 3 years - i'd say from 80% happy to 20%.
personally, i think suicides are probably going to be on the rise in a big way specifically due to this; and that's just the people who can hang onto a job right now; cannot tell you how many designers and animators are out of jobs and desperate.
I have barely technical people I knew from college pushing the latest AI certification (I can't imagine this staying relevant for longer than 6 months) and one being hired as a frontier AI engineer.
It reminds me of 2000 all over again where knowing html got you a six-figure job.
This is all normal. It’s also well worth the time spent learning
