Especially with this latest crop of models, they seem to be pretty damn competent in classic engineering rather than just software engineering.
I think the answer, to a reasonable approximation, is “everyone”. Outside software engineering most people aren’t using it for anything useful, and I keep encountering technical people including programmers who don’t use it either, which never fails to surprise me.
One of my projects is a transportation management system (TMS) and of course I have added a lot of features to it including a very capable chat-based UI that can automate a lot of tedious data entry and other tasks for dispatchers and accounting and so on. It gets used but really not very much. I’m starting to realize that I’ve probably taken updates as far as they can go in terms of the ability of people to absorb change. Most people just carry on doing things the way they always have.
We had one person on the admin team who started using Cowork to automate all kinds of stuff. She loved it. Then she left. It hasn’t caught on with anyone else.
This is not to say that things won’t change but I think it will take a while.
As an example outside of software engineering, a lot of people in marketing roles have found agents to be incredibly useful for particular tasks. I've talked to multiple people who wouldn't standardly be classified as "technical hires" who are using Claude to manage things like digital advertising. It's valuable here because managing campaigns on a platform like Google or LinkedIn involves a ton of granular tweaking and analysis. Every performance marketer makes tradeoffs around what they're realistically able to spend time doing, and what makes the biggest impact. So if you have 250 campaigns that you manage solo, you likely don't have the time to really manually optimize the bidding and budget for each campaign every couple of days based on new data. You can only try so many new angles, because creating new media is time consuming. You don't have time to construct custom experiences on-page for every particular campaign. There's a whole industry of tools that turn a tidy profit automating parts of this for this reason. And agents are really good at it, because a lot of it is just applying the same analysis over and over again.
But for a lot of startups, increasing traffic from ads 20% while decreasing spend is a good outcome, but it doesn't actually turn into revenue. The product itself might just be limited, and already being discovered by the narrow segment of potential users who find it valuable enough to pay. Or the sales process might be kind of busted, meaning the team will really only close a certain volume of new deals in a given month, no matter how much inbound they have. Or some combination of all of the above.
If it's just one marketer using an agent to optimize their advertising, there's not a lot they can do about the other constraints. And so what you end up with is one employee who feels really productive and sings the praises of Claude, but not a meaningful lift in the higher level outcomes you care about, and the analysis gets messy. In an ideal world, everyone realizes where the other bottlenecks are, but that's a genuinely hard thing to do and people have complicating incentives.
I don't think this is a particularly new problem. It feels identical to any other situation where a department asks for a tool, loves it, and it doesn't really make a difference to the bottom line or make anyone else's life easier in noticeable ways.
Because rewieving chat bots data entry is even more tedious then doing it yourself. And as long as they have to review it, it does not even matter that it makes only few mistakes.
I see it with JIRA and Rovo. It just sux using it, despite it being reasonably competent at creating tables and what not. If I could do markdown as used to be normal, it would be appreciated a lot more.
They never realized how much effort went into turning those one like tickets into code was, and the code was the least part of the effort
Feature flags, staggered rollouts, quick rollbacks, smoke testing, etc.
Sure, if you were hand managing every rollout up until now, and relied primarily on unit tests, you’re in for a world of hurt when you give a junior engineer Claude code and let em rip.
But if you have more advanced systems to measure and maintain overall service health, and codify your business logic invariants, you can really start flying these days as long as you’re all aligned on what to build and the potential impact.
High chance said senior has been laid off because "A junior with $200 claude plan" is cheaper.
There are two people, of course. Developers who can use AI to make their jobs more productive, more comfortable, less stressful. Then there are developers who can use AI to make themselves fired. (Not FIRE)
That there is a glut of high-paid, high-performing programmers who can kick back and, huh let me tighten the belt for two months and buy my own AI rig, isn’t surprising to anyone. Even those of us in the rural outbacks of Europe see them here every day. For them it’s just a consequence-free sabbatical.
Idk how many people need to hear this, but not everything 'is computa',no matter what Trump says.
Much of the worlds problems are not verifiable with a compiler that can be trained or brute forced against.
Llms are not as useful as ya'll think they are, not everything exists in a web browser, which is why Anthropic et al have saturated their TAM and are now frantically hiring sales people to convince managers in other verticles.
Turns out most people dont need or want AI.
A hammer is fantastic for driving nails, but it's not really all that good at washing a dog.
These are all jobs the silly con valley idiots claim continuously to be automating away, but it's all just fuckin lies.
The extent of tech's penetration into this economy is internet ads on facebook and streaming services. Nothing to do with actual work.
It's easy to understand how LLMs got so good at coding, they can rapidly iterate, self test, and it all happens in their digital universe.
These models now starting to spit grey beard knowledge of precision analog electronics, lightweight fastener design, and chemical surfactant systems is something very very recent. A few years ago I think we were pretty confident that the tech would hit a wall at the digital divide. Well, I can tell you now that it did not. It seems it kinda blasted right past it.
The idea is: if you have a substantive point, make it thoughtfully; if not, please don't comment until you do.