| ▲ | WarmWash 3 hours ago |
| The real question is how many people haven't figured out how to use AI to make their job easier/more productive. Especially with this latest crop of models, they seem to be pretty damn competent in classic engineering rather than just software engineering. |
|
| ▲ | adriand 3 hours ago | parent | next [-] |
| > The real question is how many people haven't figured out how to use AI to make their job easier/more productive. 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. |
| |
| ▲ | mariofdistrust 3 hours ago | parent | next [-] | | my brother uses it to do ocr on his books but, lately, claude has been refusing because of copyright or whatever so i've had to do it for him (using ai, yes, but not anthropic's) | |
| ▲ | scottyah 3 hours ago | parent | prev | next [-] | | I know firefighters and machinists heavily using it, the only places I see slower adoption is purely because of bad leadership- exclusivity contracts with certain providers or just plain fear. | |
| ▲ | calebkaiser 3 hours ago | parent | prev [-] | | I think this dynamic is underappreciated. Another thing I see in working with different companies (consulting) and discussing with colleagues at different jobs is that we as humans tend to do a pretty bad job of modeling business outcomes and the dynamics that govern them. There are lots of outcomes where you can identify one contributing role, increase the productivity for that role by a significant factor, and still ultimately not move the needle much, because the constraints span multiple functions. 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. |
|
|
| ▲ | Avicebron 3 hours ago | parent | prev | next [-] |
| A lot of people have jobs that aren't limited by how much "stuff" they generate. |
| |
| ▲ | Gigachad 3 hours ago | parent [-] | | We are capped by testing and PR review. The junior devs can spam out a million PRs a day but we keep having production incidents from not carefully scrutinising the changes. So the speed of code generation is limited by how fast we can actually accept those diffs. | | |
| ▲ | adt2bt 3 hours ago | parent | next [-] | | Production incidents from not carefully scrutinizing changes is a sign that someone more senior should be putting infrastructure in place to minimize the impact of those incidents. 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. | | |
| ▲ | Gigachad 3 hours ago | parent [-] | | I agree, with a big tech deployment process this would be less impactful. But getting from a company used to manual testing and weekly deployments to a fully automated CD pipeline is more work than a single Claude prompt. |
| |
| ▲ | 3 hours ago | parent | prev | next [-] | | [deleted] | |
| ▲ | 3 hours ago | parent | prev | next [-] | | [deleted] | |
| ▲ | hinkley 3 hours ago | parent | prev | next [-] | | Don’t forget requirements gathering and design. There’s only so fast the business side can feed requests into us. | | | |
| ▲ | basket_horse 3 hours ago | parent | prev | next [-] | | Haven’t you heard, Anthropic uses Claude for all of its PR reviews and has no issues at all! | | |
| ▲ | Gigachad 3 hours ago | parent [-] | | Unfortunately I work with users who get upset when the app goes down or features break. | | |
| ▲ | simianwords an hour ago | parent [-] | | Unironically you should be using claude for monitoring and within CI. "PRs causing bottleneck" is an anti pattern during AI. It is as easy to verify as it is to generate. |
|
| |
| ▲ | phoronixrly 3 hours ago | parent | prev [-] | | That was always the issue... Rewrites were done before LLMs and the results were the same... There was never a point in time where the bottleneck was production of code, it was always review, testing, QA, fixing bugs and edge cases, and that is when only focusing on the technical part of delivery, and leaving out communication and synchronisation within the company and between company and clients... | | |
| ▲ | rcxdude 3 hours ago | parent | next [-] | | That strongly depends on context. In larger organisations, this is definitely the case. For smaller startups and teams then the overhead is much smaller and the actual core programming work is much more of a bottleneck. | |
| ▲ | bluefirebrand an hour ago | parent | prev [-] | | Sometime in the last 15 years we got these huge backlog wishlists of one line thoughts. People were convinced because software devs couldn't keep up translating one line thoughts into working software that the code must be the bottleneck 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 |
|
|
|
|
| ▲ | lifeisloving 3 hours ago | parent | prev | next [-] |
| How so? Or is this just vibes based analysis? I dont really know what you mean by classical engineering, but sure if something can be done on a computer it can infinite monkey theorem its way to a solution. This isnt exactly useful its just an enablement of laziness. 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. |
| |
| ▲ | jjulius 3 hours ago | parent | next [-] | | Right, this is what astonishes me about the constant rhetoric/hyperbole about how this is going to impact "all the jobs" and make everyone wildly more productive than ever before. It's a fabulous tool in a limited number of areas, and it's otherwise only handy here and there. But just because it's a fabulous tool for the coding that is so prevalent among HN users does not mean that it's a fabulous tool for everything. A hammer is fantastic for driving nails, but it's not really all that good at washing a dog. | | |
| ▲ | scottyah 3 hours ago | parent [-] | | Name a single job that can't be improved with better communication, planning, or insight. | | |
| ▲ | jjulius 3 hours ago | parent | next [-] | | This is conflating the benefits found within those areas with the ability of AI to actually deliver those things effectively across every single profession. Improving something by 2% vs. revolutionizing an entire industry are wholly different propositions. Maslow's hammer would like a word. | |
| ▲ | rcxdude 3 hours ago | parent | prev | next [-] | | I'm not sure I'd rank LLMs very highly at any of those on their own. In the hands of many users they can even help wreck havoc with those processes. | |
| ▲ | 27183 an hour ago | parent | prev [-] | | Mechanic, welder, builder, farmer, logger, millwright, trucker, heavy equipment operator... I could go on. Literally the entire economy in the area I live is completely impenetrable to tech, let alone AI. None of it is worth a shit to any business here. 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. |
|
| |
| ▲ | WarmWash 3 hours ago | parent | prev | next [-] | | I use classic engineering to refer to the (engineering) disciplines where mother nature messes your day up rather than obscene levels of man made (or machine made) pure complexity ruining your day. 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. | |
| ▲ | cleandreams 3 hours ago | parent | prev [-] | | Vibes based analysis is very high volume right now due to upcoming IPOs. | | |
|
|
| ▲ | nickphx 3 hours ago | parent | prev [-] |
| [flagged] |
| |