News for hackers. Stuff that matters.
Re:Appearing productive in the workplace by switchbak on Wednesday May 06, 2026 @02:01PM (#48039396)
I think for a lot of companies, AI is a destabilizing force that their managerial structure is unable to compensate for.

When you change the economics to such a degree, you're basically removing a dam - resulting in far more stress on the rest of the system. If the leaders of the org don't see the potential downsides and risks of that, they're in for a world of hurt.

I think we're going to see a real surge of companies just like this - crash and burn even though this tech was sold as being a universal improvement. The ones that survive will spread their knowledge about how to tame this wild horse, and ideally we'll learn a thing or two in the future.

But the wave of naivety has surprised me, and I think there's an endless onrush of people that are overly excited about their new ability to vibe-code things into existence. I think we've got our own endless September event going on for the foreseeable future.

Re:Appearing productive in the workplace by funimpoded on Wednesday May 06, 2026 @02:44PM (#48039975)
I increasingly see “AI” as a sort of virus tuned to target management, specifically. Its output is catnip to them, and it’s going to be unavoidable for those who want to look good to superiors and peers (i.e. the #1 priority for managers) even as it adds no actual value whatsoever to what they do. People under them, too, will have to start burning tokens on bullshit to satisfactorily perform competence and “doing work”. Meanwhile, none of this is actually productive. It’s goddamn peacock feathers.

It’s like some kind of management parasite. I’m not even sure at this point that it’s going to lead to an overall productivity increase whatsoever for most sectors, because of this added drag on everything.

Re:Appearing productive in the workplace by LinuxAmbulance on Wednesday May 06, 2026 @03:29PM (#48040578)
AI has made my work about 5-8x quicker, just because I'm able to have it cover a lot of the grunt work (update 42 if statements in 32 different files) that took time, but no particular skill.

I think the use cases where AI makes an economic improvement to the status quo for a business are rare, but they do exist, and they can be a significant improvement.

It's like the early days of the dotcom boom and bust - people thought the internet was good for every use case under the sun, including shipping people a single candy bar at a loss. After the dotcom bust, a lot of that went by the wayside, but there was a tremendous economic advantage to the businesses that were more useful when available on the internet.

Re:Appearing productive in the workplace by zbentley on Wednesday May 06, 2026 @05:59PM (#48042450)
Without getting into AI-for-work good or bad,

> update 42 if statements in 32 different files

is a silly behavior for a programmer or an AI to have to do more than twice. We have tools that very effectively remove the need for things like that: programming languages that allow modular and reusable code, good design, etc.

Re:Appearing productive in the workplace by Pannoniae on Wednesday May 06, 2026 @06:43PM (#48042876)
Ideally. But that requires the correct abstraction, requires keeping it up to date.... that's basically an unachievable ideal. You either have overabstraction/overengineering (most codebases) or you have repetition. Repetition is actually more preferable in the LLM-world because you have to keep less stuff in your head. And the LLM's head too.

Even if something does look copypasted, it might actually be semantically distinct enough that if you couple them, you'll create a brittle mess.

Additionally, there's always going to be global changes (update the code style, document things, refactor into a new pattern, add new functionality to callers, etc.). The question isn't whether you use your lanuage's tools or you do it by hand, the question is whether you use an LLM or do it by hand :P

Re:Appearing productive in the workplace by zbentley on Wednesday May 06, 2026 @07:54PM (#48043522)
Totally fair, but 42 if-statements across 32 files isn't something you need to fix with like ... a grand refactor or hexagonal architecture or event sourcing or whatever the overengineering pattern du jour is. You can fix that with a utility function or three, and a file/class/module/whatever that owns the code relating to some of those conditions.

I'm not some DRY zealot, but I've been in the "this system needs really similar changes to a ton of geographically distant code for simple changes" salt mines a lot. The people who say that kind of spaghetti is unavoidable are just as wrong as the ones who say it can only be fixed with a grand rearchitecture by a rockstar.

Re:Appearing productive in the workplace by Pannoniae on Wednesday May 06, 2026 @09:03PM (#48044144)
Sure but even wiring that utility function in is work :D If you have even just a 2-3-million LoC codebase, not even something truly enormous - making global changes does require typing, and a whole lot of it...
Re:Appearing productive in the workplace by reverius42 on Thursday May 07, 2026 @01:03AM (#48045578)
If you have a codebase that big, can you even fit enough of it into a context window for the LLM to make correct and meaningful changes across all of it? Admittedly I've only used LLM-based coding for smaller projects.
Re:Appearing productive in the workplace by Pannoniae on Thursday May 07, 2026 @06:11AM (#48047565)
All of it hell no :D But just with any things, you break things down into subtasks. Then you break it down even more. You as a human don't hold all that stuff in your head either, so why would an LLM?

My current codebase is ~3 million LoC all in all (not greenfield, really old code), working on it by myself, the complexity is definitely manageable between Claude and me :)

Re:Appearing productive in the workplace by cess11 on Thursday May 07, 2026 @08:10AM (#48048418)
Such repetitions can regularly be deterministically automated, like find -exec sed and similar medium level tools.

If you spend a lot of time performing monotonic tasks, then your organisation needs to delete and refactor for a while until change in 'hot' areas of the code base are easy to make. Reaching for some code synthesis SaaS to paper it over will worsen the problem and should result in excommunication from the guild.

Re:Appearing productive in the workplace by jimbokun on Wednesday May 06, 2026 @10:46PM (#48044844)
LLMs are great at replacing repetition with an abstraction.
Re:Appearing productive in the workplace by Degorath on Thursday May 07, 2026 @02:09PM (#48052742)
I just want to mention that in my personal anecdotal experience, every codebase I have ever worked on, except 1, was underengineered and not overengineered. The last one was just "engineered".
Re:Appearing productive in the workplace by jimbokun on Wednesday May 06, 2026 @10:45PM (#48044836)
The AI needs to update the 42 statements to all use the same function so it can be updated in just one place going forward.
Re:Appearing productive in the workplace by bertylicious on Thursday May 07, 2026 @12:50AM (#48045498)
Could you please show us an example of the change made to one of these if statements? I'm curious, because it seems absolutely wild to me to end up in such a situation (where that many changes are required and the usual refactoring tools of modern IDEs are insufficient) in the first place.
Re:Appearing productive in the workplace by missingdays on Thursday May 07, 2026 @05:20AM (#48047246)
> the usual refactoring tools of modern IDEs are insufficient

Cursor doesn't have refactorings, so

Re:Appearing productive in the workplace by tardedmeme on Thursday May 07, 2026 @06:18AM (#48047617)
Does your work primarily consist of updating 42 if statements in 32 different files? We all do that occasionally, but if you're doing it constantly, is it possible that a different system design would make your work much easier?
Re:Appearing productive in the workplace by LtWorf on Thursday May 07, 2026 @06:58AM (#48047909)
If you are 8x quicker by having the AI do these for you, I think you are a junior intern or something? It must mean most of your time is spent doing these things.
Re:Appearing productive in the workplace by pmg101 on Wednesday May 06, 2026 @03:03PM (#48040229)
I agree with everything you've said, but don't you think quite a lot of things have also been like this before, just to a lesser degree?

I've often had the sense that most of what is done inside companies is a kind of performance of work rather than work itself. Mostly all a big status game between various different factions. All actual value provided by just a few engineers here and there who are able to shut out the noise and build things.

Re:Appearing productive in the workplace by eproxus on Wednesday May 06, 2026 @03:15PM (#48040390)
Things have probably always been like that, agree. I often try to see AI as a catalyst, that accelerates what already is.

In a good culture, with high competence and trust this can yield increased output (to some degree at least) and in a bad culture it will accelerate and expedite the dominating traits instead.

Re:Appearing productive in the workplace by grvdrm on Wednesday May 06, 2026 @05:41PM (#48042242)
I often think that executive level work is about changing the executive team and writing memos about changing the executive team. Then there’s a different team with different members and they begin the cycle again. Repeat over and over again.

The number of times I’ve seen a HTML memo sent from the assistant of the executive that says “from the desk of…” with babble about new leadership.

Re:Appearing productive in the workplace by jimbokun on Wednesday May 06, 2026 @10:49PM (#48044860)
The rest of the work is inventing new ways to increase their compensation.
Re:Appearing productive in the workplace by funimpoded on Wednesday May 06, 2026 @05:46PM (#48042299)
> I agree with everything you've said, but don't you think quite a lot of things have also been like this before, just to a lesser degree?

That’s exactly the reason LLMs and friends are so dangerous to companies, and it’s so hard for them to resist using them in useless/counter-productive ways. They’re excellent at faking signs of effort and work that companies can hardly help but reward, absent any actual way to measure manager effectiveness (and approximately nobody knows how to measure that, in the wild). This takes the form of gilding and padding on a lot of communication, none of which adds actual value but it does cost money directly and indirectly (time wasted sorting out which parts of a document are intentional and meaningful, and which are plausible but irrelevant LLM inventions, for instance)

Re:Appearing productive in the workplace by jimbokun on Wednesday May 06, 2026 @10:47PM (#48044848)
Yes and this is why small startups can often beat them .
Re:Appearing productive in the workplace by pmg101 on Thursday May 07, 2026 @11:07AM (#48050345)
I really used to think this. Those old incumbents, I used to think. Such slow old dinosaurs! A crack team of just me and a few friends could eat their lunch for sure, and soon they'll be gone.

And yet, here we are.

Of course, some things get disrupted, sometimes. But I'd hardly say all the bloat has been competed out, would you?

Re:Appearing productive in the workplace by wartywhoa23 on Thursday May 07, 2026 @06:38AM (#48047778)
Counter-question: if quite a lot of things have also been like this before to a lesser degree, should we not oppose efforts to make everything like this to a greater degree?
Re:Appearing productive in the workplace by pmg101 on Thursday May 07, 2026 @11:04AM (#48050318)
Yes!
Re:Appearing productive in the workplace by jappgar on Thursday May 07, 2026 @09:00AM (#48048892)
Yes but now it gives slackers a way to imitate and inundate the builders.
Re:Appearing productive in the workplace by tanvach on Wednesday May 06, 2026 @03:25PM (#48040518)
This is very apt
Re:Appearing productive in the workplace by jiggawatts on Wednesday May 06, 2026 @06:00PM (#48042458)
It does have real benefits, but also, of course, all of the downsides you mentioned.

The best analogy is the outsourcing / offshoring fad of the last decade.

Managers hated that senior developers were getting highly compensated (often higher than the management class!) and pounced on every opportunity to replace expensive people with (much!) cheaper options, quality be damned.

For the few companies that paid attention to the quality, this worked out swimmingly. Apple is probably the best example, they've outsourced almost all of their manufacturing to China and other similar countries.

So yes, my mental picture is that every manager is drooling right now because they think they can replace someone getting paid six figures with an AI that costs six dollars a day, if that. A virtual employee that doesn't talk back, doesn't argue, doesn't question, doesn't go off on "unproductive tangents" like refactoring (whatever that's even supposed to mean), and just pumps out code 24/7 like a good little slav... employee.

The very rare smart managers out there are looking at this more like the transition that happened to architect firms when CAD became available. They used to have a dozen draftsmen for every architect. Now there are virtually none, I haven't even heard that job title being used in decades! We still have architects, and if anything, they're paid even more.

Re:Appearing productive in the workplace by vannucci on Wednesday May 06, 2026 @08:02PM (#48043618)
I'm wondering what this could mean to the future of software work and AI use, care to weight in? I don't have a good mental model for this period of time (I do agree with your sense of things).
Re:Appearing productive in the workplace by jiggawatts on Wednesday May 06, 2026 @10:00PM (#48044522)
A lot of people have already noticed that it's becoming cheaper to create bespoke software, as an alternative to paying a SaaS or purchasing off-the-shelf.

An example is that instead of buying a cookie-cutter "MacMansion" like in the last century even individuals can afford a unique house designed by a professional architect. It may not be an award winning artistic design, but it won't be the same copy-paste design as every neighbour up and down the street.

I'm seeing more comments online that developers are now expected to do more in the sense that what used to be a CLI script may now be a semi-vibe-coded application with a Web UI, a dashboard, and Open Telemetry integration because... why not?

As an example, I got a bunch of boxes of random Lego for my kid and I wanted to figure out what sets the pieces came from. I got Codex to vibe-code a full SPA web UI and a matching API app that pulls Rebrickable database CSVs, parses them, puts them into SQLite, and then runs a fairly complex integer optimisation solution on top of that collected data to figure out the best match. I did that in an hour while sitting in on an online meeting!

There is no way I'd have the mental energy to do a project like that otherwise. I'm too busy with housework, actual work, etc... Maybe when I was younger I could blow a few weeks of effort on something like this, but now? No way.

That cost-benefit arithmetic has dramatically shifted thanks to AI developer agents. Suddenly, many fiddly tasks are no longer fiddly, or even trivial, so there's no excuse not to do them any more.

Going back to the architect or mechanical engineering example: Significant corrections to designs used to be expensive because all the blueprints (on paper!) had to be redrawn and distributed. Now, a change to CAD design in 3D can be converted to arbitrary 2D views, cross-sections, or whatever in seconds. The software just projects whatever view you want out of the master design file. Creating the paper blueprints similarly takes a minute or two at most on an industrial large-format printer. It just spits it out.

Re:Appearing productive in the workplace by jimbokun on Wednesday May 06, 2026 @10:52PM (#48044886)
> I did that in an hour while sitting in on an online meeting!

And they say meetings aren’t productive!

Re:Appearing productive in the workplace by bonesss on Wednesday May 06, 2026 @02:48PM (#48040026)
I’m an LLM enjoyer who also thinks that ‘er ‘jerbs are safe and, taken to their logical conclusion, most LLM-stroking online around coding reduces to an argument that we should be speaking Haskell to LLMs and also in specs and documentation (just kidding, OCaml is prettier). But also, I do a little business.

You’ve hit the real issue, IT management is D-tier and lacks self awareness. “Agile” is effed up as a rule, while also being the simplest business process ever.

That juniors and fakers are whole hog on LLMs is understandable to me. Hype, fashion, and BS are always potent. The part I still cannot understand, as an Executive in spirit: when there is a production issue, and one of these vibes monkeys you are paying has to fix it, how could you watch them copy and paste logs into a service you’re top dollar paying for, over and over, with no idea of what they’re doing, and also not be on your way to jail for highly defensible manslaughter?

We don’t pay mechanics to Google “how to fix car”.

Re:Appearing productive in the workplace by smileysteve on Wednesday May 06, 2026 @04:04PM (#48041030)
This is definitely ¾ of what you pay a mechanic to do; 1 publisher writes a maintenance manual for a car; mechanics all around the globe can use that to work on that specific car.

It's the mechanics that don't reference Google or the Haynes manual that are more likely to get it incorrect.

As a kicker, mechanics also have a pricing book for the task, they know how many hours a task will take on a certain car (rounded up for the most part).

Re:Appearing productive in the workplace by voxl on Wednesday May 06, 2026 @04:56PM (#48041701)
You are not responding faithfully to the comment. A mechanic looking up the schematics in a manual understands them. Just because they haven't memorized the material does not make it the same. This is more analogous to looking up a function in the documentation that you forgot about.

This is clearly not what the post was referring to, which is instead like googling how to fix a pipe in your home when you've never done any plumbing before in your life. Can it work out? Sure, depends on the issue, can you cause your pipes to freeze, your house to flood, or sediment build up to completely block a pipe? Yes.

Re:Appearing productive in the workplace by franktankbank on Thursday May 07, 2026 @09:03AM (#48048921)
> mechanics also have a pricing book for the task, they know how many hours a task will take on a certain car

I do want to point out that this is used to suppress mechanic salary. Certain jobs are absolutely fucked how its time calibrated. Doesn't matter to business owner they can charge $$$ how they want.

Re:Appearing productive in the workplace by IAmBroom on Wednesday May 06, 2026 @04:16PM (#48041174)
With you up until the last sentence.

When I get my car fixed, I could not care less if they googled, used a service manual, or did it by "these old 2023's always had this problem right here...". I care if it is fixed.

And as I'm currently trying to fix something on my own, for financial reasons, I assure you a mechanic with training AND google can do a better job in 1/4th the time. Because I don't have the training.

Nor do the worst people using LLMs.

Re:Appearing productive in the workplace by switchbak on Wednesday May 06, 2026 @08:03PM (#48043628)
But do you expect to pay top dollar to have someone pretend they know how to fix a car? That's the point here.

Granted, the trades is a bad example because it's chock full of fakers too.

Re:Appearing productive in the workplace by 20after4 on Wednesday May 06, 2026 @03:42PM (#48040747)
> We don’t pay mechanics to Google “how to fix car”.

No, instead of google they just look it up on alldata.

Re:Appearing productive in the workplace by tyyyy3 on Wednesday May 06, 2026 @03:23PM (#48040501)
The more difficult it is to trace one’s labour to output.. expect more theatrics ;)
Re:Appearing productive in the workplace by jcgrillo on Wednesday May 06, 2026 @04:59PM (#48041761)
Speaking not as a professional mechanic, but as someone who maintains a car, two trucks, a tractor, a couple boats, and has googled quite a lot of torque specs in my time... If you're googling torque specs in 2026 you're gonna have a bad time. They're frequently just flat out wrong, especially the AI summaries ;). Use the authoritative source of truth--the shop manual published by the equipment manufacturer. Accept no substitutes.
Re:Appearing productive in the workplace by mountain_peak on Wednesday May 06, 2026 @06:49PM (#48042927)
Absolutely - factory repair guides/apps are the only source of truth for official specs, although 3rd-party manuals are very good as well. That being said, I've often turned 3-hour estimated repairs into 15-minute jobs through clever shortcuts. For example, rotating an alternator to replace the run clutch through the gap in in the intake manifold as opposed to removing the complete intake manifold. I think that's where using experienced (and resourceful) developers pays off.

Also, for sale: BMW E60/61 Bentley 2-volume set. Barely used.

Re:Appearing productive in the workplace by jcgrillo on Wednesday May 06, 2026 @06:55PM (#48042980)
Yeah Bentley (and in some cases Haynes) make good aftermarket manuals too. And you can find good information on some forums. But you can also find a lot of bad information. Reliably sifting the good from bad only comes with experience--much like in software.
Re:Appearing productive in the workplace by atomicnumber3 on Wednesday May 06, 2026 @03:09PM (#48040300)
Honestly, the most impactful thing I've seen AI do for any workplace is serve as the ultimate excuse for whatever pet thing someone's wanted to do, that can't stand on its own merits, and what they really need is a solid excuse.

Rewrite that old crunchy system that has had 0 incidents in the last year and is also largely "done" (not a lot of new requirements coming in, pretty settled code/architecture)? It's actually one of our most stable systems. But someone who doesn't even write code here thinks the code is yucky! But that doesn't convince the engineers who are on-call for it to replace it for almost no reason. Well guess what. We can do it now, _because AI!!!_ (cue exactly what you think happens next happening next)

Need to lay off 10% of staff because you think the workers are getting too good of a deal? AI.

Need to convince your workers to go faster, but EMs tell you you can't just crack the whip? AI mandates / token spend mandates!

Didn't like code reviews and people nitpicking your designs? Sorry, code reviews are canceled, because of AI.

Don't like meetings or working in a team? Well now everyone is a team of 1, because of AI. Better set up some "teams" full of teams of 1, call them "AI-first" teams, and wait what do you mean they're on vacation and the service is down?

Etc. And they don't even care that these things result in the exact negative outcomes that are why you didn't do them before you had the excuse. You're happy that YOUR thing finally got done despite all the whiners and detractors. And of course, it turns out that businesses can withstand an absurd amount of dysfunction without really feeling it. So it just happens. Maybe some people leave. You hire people who just left their last place for doing the thing you just did and now maybe they spend a bit of time here. And the game of musical chairs, petty monarchies, and degenerate capitalism continues a bit longer.

Big props to the people who managed to invent and sell an excuse machine though. Turns out that's what everyone actually wanted.

Re:Appearing productive in the workplace by LinuxAmbulance on Wednesday May 06, 2026 @03:31PM (#48040599)
> Need to lay off 10% of staff because you think the workers are getting too good of a deal? AI.

I think we're seeing a ton of that right now, and it's not slowing down any time soon it seems.

Re:Appearing productive in the workplace by vkou on Wednesday May 06, 2026 @02:44PM (#48039977)
> I think for a lot of companies, AI is a destabilizing force that their managerial structure is unable to compensate for.

Absolutely. Giving a traditional company AI is like giving an unlimited supply of crystal-blue methamphetamine to a deadbeat pill addict.

It enables and supercharges all their worst impulses. Making a broken system more 'productive' doesn't do shit to make the users better off.

The work output everyone produces doubles, but the ratio of productive to net-negative work plummets.

Re:Appearing productive in the workplace by darth_avocado on Wednesday May 06, 2026 @09:43PM (#48044410)
> I think for a lot of companies, AI is a destabilizing force that their managerial structure is unable to compensate for.

From the article:

> because the competence the work reflects is not the novice’s competence at all

The core of the problem is that AI allows engineers who were previously inexperienced or downright mediocre, pretend that they are talented, and a lot of management isn’t equipped to evaluate that. It’s like tourists looking at a grocery store in North Korea from their tour bus. It looks like a fully functioning grocery store from the outside, but it is mostly cutouts and plastic fruit.

Re:Appearing productive in the workplace by Terr_ on Thursday May 07, 2026 @03:27AM (#48046481)
you're basically removing a dam - resulting in far more stress on the rest of the system.

Adding to the grab-bag of useful flow-dysfunction concepts and metaphors: Braess's paradox. [0]

Sometimes adding a new route makes congestion strictly worse! Not (just) because of practical issues like intersections, but because it changes the core game-theory between competing drivers choosing routes.

[0] https://en.wikipedia.org/wiki/Braess%27s_paradox

Re:Appearing productive in the workplace by cmrdporcupine on Thursday May 07, 2026 @10:45AM (#48050104)
100% agree on this. Big log jam coming, with volume of code piling up behind the requirements and planning and "meaning" of the work aspects.

In particular, I think the agentic tools as written today are particularly corrosive on code review culture. We spent years having mainline companies migrating from free for all commit privileges (everywhere I worked was like this prior to about 2010 or so) to variants of code review / "PR" code reviewing culture, only to have it all disintegrate in the last 6 months as "reviews" have ended up consisting of people tossing agentic code over the fence and then people having other agents review it, and then again agents respond to comments, etc. etc.

It's a bit of code review theatre that pretends there's still eyes on things, when there's not.

Similarly the whole edifice of "agile" planning in SCRUM etc form makes no sense when pumping out code isn't the time blocker. All the backlog refinement meetings and burn down charts and points tracking are pointless ceremony when what people really need is intense clarity on what needs to be done and why and intensive review of what's already been built and where the holes are.

All of this is just going to create a giant logjam in the higher level "executive function" aspects of a company. Getting people talking to each other has always been something most management at most companies I've worked at have failed at. Now they're going to really suffer for it.