[bunderbunder]

Amen.

At work our documentation isn’t just getting littered with annoying jargon. It isn’t just all the hallucinations, either. (Since when has documentation ever been 100% trustworthy?) It’s that it’s so poorly written and structured that it’s becoming borderline incomprehensible.

My company is currently considering making, “Why should I bother to read something you didn’t bother to write?” an official policy because even the executives are starting to burn out on all the time they have to spend wading through slop.

[mywittyname]

I wish my company would do this. A coworker pulled an all nighter before a vacation and just left me with a million line claude summary of their work then just fucked off. The message was two-part due to size and lacked basic stuff like, "how to run".

He's going to be annoyed that none of that work was used. But the reality is, at least 75% of claude generated text is pointless.

[xyzzy_plugh]

Somewhat off topic but every time I've experienced this sort of thing it was management's fault. If an engineer needs to pull an all nighter and hand off a pile of garbage then someone in management fucked up. If they can't see this scenario happening a mile away then they aren't paying attention.

It's easy to blame the engineer, but all too often they don't deserve it.

Sorry that happened to you.

[chrisandchris]

If it wasn't worth your time writing, it isn't worth my time reading.

[madcaptenor]

ai;dr