What kills me is you might expect this from a busy high level manager that doesn’t really understand the technical details and they just point the AI to an error they got. They don’t know how to interpret the response, so they ask someone who work on the thing. It’s still kinds annoying because you could just ask, but whatever. But to get these from junior and senior engineer for the areas they work in and expect someone else to read it for them? It’s crazy behavior. How can someone serious even think that’s ok.
They generated lots of documentation across the whole stack and now makes all PO/BAs read it if it's correct. So not just 300 lines - he unironically generated thousands of lines of "documentation" and is now making hundreds of people review it for him
Complete brainrot
Au psychosis is getting seriously outrageous at this point
Thankfully I'm a dev and thus aren't in the blast radius of that genius idea
Many many people have jobs where their contribution is granting access to deliberately undocumented things, like knowing where the config files are and some such. They hate the idea of AI. For my non IT friends its great for diagnosing wifi issues. It's also great for competent network engineers. It's not great for those who gain a salary due to having memorized some actions or settings that they don't even understand much. Note that this group has also already resisted traditional script automation, just like US dock workers who resist automation.
I would say to him that if he wants me to do his job, he needs to pay me his salary.
So... back to a currency backed by gold?
In all seriousness, actual AI psychosis is my 3rd risk behind 1. public interactive agents and 2. whatever devs are doing with agents to prod
Actual intelligence might be[0] to know what typos (of any kind) are fun to riff off.
Maybe this didn't hit the mark for you, but it got a chuckle out of me (especially considering the last hype before AI was crypto).
-----
[0] I don't even try to figure that out anymore, in a few years I'll pick the definition that I think best captures my thoughts
See that way too often in comments like this. Anyway, it was pretty likely they knew it was a typo, it was just a funny response.
yes you are
Like, I can see getting a strong warning the first time somebody notices you do this, then if you persist you’d have to be let go.
Just like anybody else who is clearly not doing their job.
Why would you tolerate this sort of behavior at your company?
To avoid rushed or incorrect decisions, conflicts intentionally move through gradual escalation. If someone behaves unprofessionally, for example by submitting a code review they do not understand, the first step is to establish the likely cause.
They may ultimately be at fault, but that does not absolve the surrounding environment. The culture may be toxic, deadlines unrealistic, or communication poor.
The best course of action for someone directly affected by uncooperative coworkers is to avoid assuming ill intent. Get them on a call and let them explain their pull request, however trivial the issue may seem. Even if the gesture is misinterpreted, you still have a far stronger position than righteous indignation.
I once worked in a place where a guy would pick on me in code reviews, he wasn't really higher position, but had been with the company longer than I was.
He was just an asshole asserting his dominance and needed to be taken a notch down by a manager and it turned out he didn't understood (or more likely didn't try to understand) the PR when confronted.
An Ops person who deals with company code base but is not a SWE in the code base regularly has to work around issues with this software (They are OPs). However they have read access to the source.
In the past, they see a bug and open a jira with how it was found for the dev team, and it may or may not ever get looked at.
Now ops can point claude to the repo and it can most likely [but not always] find the issue.
So this ops person can do most of the work of reproducing the bug and finding the problem/solution but doesn't understand the code. Should they not produce the findings for someone else to read/validate? Should they go back and just open the ticket the old way?
If I get a request like this on a day when I don't feel sufficiently quixotic, I say sure and just put it through an LLM myself - if they don't bother to re-read it, why should I? This does not have a great promise for a future of work, of course. Also, in my teams, I explicitly tell people not to do that.
That time has now passed though.
Sadly, the point is validating the human worth of the human who can't do any better than this.
But, assuming you're not stuck on that human's Self Esteem Care Team, it can be tricky to tell them that they need to seek validation elsewhere.
> Don't post generated text or AI-edited text. HN is for conversation between humans.
This is the worst person to get this from because they literally don’t understand it.
This shit has progressed well past seriousness and into the absurd
I had a guy with more senior title say “I love the new api and cli. Is anyone working on the docs? Because I can take a crack at them” then goes to generate 12 markdown files, and shares them with me. All the cli commands and APIs are wrong. I was very confused. You have the api spec, and the cli. You couldn’t point your agent to them to validated the commands and the api? He replies “oh that’s a good idea. I just described them to the agent and thought you could review and fix mistakes”
The effect is less pronounced in other industries but they're gonna catch up. Might take a decade for some of them , perhaps even 20 years for the rare ones like nursing but the trend is quite clear.
The system does NOT reward caring. That's the problem.
Oh, for the testing required by any customer of any software vendor any time from now to forever more, as a result of the possibility of this level of irresponsible outsourcing of brain.
Enshittification is a new word/concept, but it seems we've already reached the potential for enshittification squared.
I'm glad most of my colleagues are still doing things themselves. But honestly, if all you can do is tell me what Claude told you and you didn't even bother to read it yourself. Then I might as well just cut you off the team and go use Claude directly.
I created a spreadsheet called “slop” and add the name to the list and redirect all queries to their engineering manager. I’m not wasting my time on that shit.
The only reason I don't do an equivalent of this, shared convo links, is that I simply don't use Claude directly. I use it through hundreds of other people.
“Learned engineering just to become the condom between Claude Code and prod”
And that (re)framing helped as well to think about the “what are we even (left) doing” as an industry
I have been doing daily agentic coding myself since last November, but lately Im having concerns. We are on the verge of becoming Warhammer 40k Tech-Priests: chanting sacred prompts to appease the machine spirit, praying for a good result. The foundational knowledge is lost, meaning that even if we do look at the code, we won't understand it anyway.
but this is similar to a lot of other technical fields that have width and depth. People would not understand assembly any more and blindly trust the output of the compiler. People now can only design a part of a CPU, and not the entirety. Chip manufacturing is so complicated that there's probably no single person who could understand the entire process, from end to end.
Yet, we all trust these things.
This was still OK as long as you had enough understanding of Assembly to debug it. Even though I haven't written that much Assembly directly, I can still debug it when there are compiler bugs, which does ocasionally happen.
If people lose both the ability to write and debug code then things get much worse. If no one in a company has the ability to do that well, in that case you truly are at the mercy of the LLMs.
I'm wondering if some of us will become consultants to companies that lost the ability to handle code. When I was in university the going meme was that old COBOL programmers were making a lot of money in consulting jobs, maybe this will be the new version of that.
Then do it and don't ask questions.
If I paste back to you an answer from Claude, it's because I took the time to reformulate your question for Claude including all the relevant implicit context, waited for it to go through its reasoning, answered any extra questions it might have posed, corrected it if it went off course, filtered out the hypotheses and picked one that convinced me, if any. Finally I took the most relevant part of it- the one that contains the important justifications- and pasted it back to you with clear attribution.
You can do this yourself if you want, I won't be offended.
If you _could_ do that and hand the information to Claude, you could also just…give the person that information directly, and avoid wasting their time and the tokens.
I'm not sure if you're trying to be funny, but this is such an unintellectual take that it veers into caricature. Props if that was your purpose.
If your question can be answered by Claude, and you didn't ask Claude yourself, and when other people do it for you, you complain that you could have done it yourself, then my honest reply is that you should just shut up and learn to use Claude.
I don't want to know what Claude thinks.
If you don't know the answer, say that. "I don't know" is a perfectly good answer, albeit one which I might follow up with something like "Well why don't you know? This is literally your job to know", which is kind of what 90% of my emails at work for the past three weeks have been.
In a human interaction, when used confidently, it means 'I'm so authoritative I don't even have to front. I don't have to do the slightest thing to impress you. My foundation is so secure it doesn't need defending or justification at all". Also, 'that turns out to be outside the massive quantity of stuff I do know, how interesting'. Think Holmes, perhaps erroneously saying 'Now that I know that, I shall do my best to forget it' on the grounds that his work wasn't helped by the fact.
It could get ruined by an AI normalization of the idea that 'everybody should know literally everything, because asking an AI is the same as knowing and then you know the thing, having been told it'. Plenty of money is now marketing this position to the world, and so it's possible 'I don't know' will become ruined, a shameful response.
I feel like that may not happen in practice, though, because that pro-AI position is what used to be called 'pants-on-head R-slur' and I feel like the people who buy into this extreme position will make SUCH a disaster of things that it will tend to make that position, instead, the shameful response… and 'I don't know' will remain a valid signaling mechanism to convey 'I'm so authoritative I don't even have to front', all the more if it's more of a shocking response to get.
They will invent crazy workarounds to avoid those 3 words.
Even if I ask "Do you know X?" they will not just say "no" most of the time, unless it's really outside their wheelhouse. If they think they should know it, they'll spit out statements worthy of an LLM.
And I admit, I felt the same at first. The first few times I told the CTO (my boss) that, I cringed. But he just told me to put aside time to research it. He knew I couldn't know everything, especially about things that we hadn't done before.
The amount of text isn’t equal and the benefit is primarily that I can push the LLM into a basin you don’t know the keywords for — something that takes a few minutes to type a couple sentences and me scan the results to make sure they’re roughly on track. And much, much less time than me trying to (re)write a treatise on a topic.
Dropping you an LLM reply is the equivalent of dropping you a link and telling you to learn about the topic — and appropriate in roughly the same circumstances.
And if I paste back to you an answer from Claude, it means that I have read and evaluated what Claude wrote back, and I have extracted the part of it that most clearly contains the answer as well as the diagnosis- if I gor anything relevant.
Of course I could instead pretend I came up with the answer myself in 5 minutes thanks to my superior analytical skills, and write down two short lines that point to the solution without any explanation. Would you find it better?
> write down to short lines that point to the solution without any explanation. Would you find it better?
Yes. That’s why I asked you and not an LLM.
That’s all you have to add to make this into a much more pleasant interaction
But it should form part of your own judgment, not, as you say, just pasted into a chat without any thought.
Do you guys think we're going to see a de-evolution of human beings due to technology?
But a modern engineer has computers, math software, can code, has all the knowledge of the internet at their fingertips. With all that assistance I believe modern engineers are way more productive and capable.
Some machines are capability amplifiers.
Other machines are shit puking buck passing time sinks.
Motorising any of those machines could be considered lazy, though.
Of course it is, at equivalent distance.
If cycling were just about laziness then you'd see people cycling at walking speed everywhere, which you never see.
Since we're kinda talking about LLMs too, it's interesting to note that while cycling really does enable you to go faster than you can run, LLMs do not enable you to type at 1000 words per minute. LLMs are more like a teleport that only lets you describe your desired destination, you cannot simply enter a coordinate to get exactly where you want to go.
Same with coding agents. I could do it by hand. It just would take much longer. Often so long that it would be impractical.
The stitching comment is just pedantic. People don't hand stitch like a machine not because they are lazy, it's because it's ineffective and impractical. It's not impossible to drive screws directly into softwood by hand, but you'd never get anything done that way. It's not lazy to choose another method, it's just being an effective worker.
As for coding agents, it's clearly effective to write software without them because we have been doing it for decades so far. It still remains to be seen whether they are laziness (ie. it's just a motor) or if they are actually enabling new possibilities (ie. we get software that really wouldn't have been possible before).
At a time when I was in better shape than the average person, the most I ever worked up to was 40 miles, and it was brutal. In my entire middle-aged life, I have met exactly one person who believably claimed to have done 100 miles in a day. I'm sure it's easier than many/most people think, but not 'anyone' easy, with just 'a bit' of training.
It's the same issue. You can walk 100 miles. Just not in a day. And you can create 10k LOC without a coding agent. Just not in a day.
I don't think that coding agents enable technical possibilities. They just allow things that wouldn't be economically possible without them.
What? Have you, uh, ridden a bicycle before...?
That may be true, but the fact is that cycling is a more energy-efficient form of transport than walking. It takes literally less effort to go the same distance.
Anyway this is just silly, we are splitting hairs. A lot of machines have a functional purpose and do not exist for the lazy. The LHC, ships, thousands of examples.
I'm halfway through my 30's and this downturn started with my generation, halfway through the 80's. I hope I'm missing something, because I still need to see a benefit for lower attention spans, lower comprehensive reading skills and lower critical thinking capabilities.
If you look at old test papers - the lack of intelligence in modern times is very stark.
The claim of a "lack of intelligence in modern times" is flat out contradicted by the data. It'd take a lot of regression to get back to 1956 levels.
"Do you guys think we're going to see a de-evolution of human beings due to technology?"
Not LLMs specifically.
Insofar as I believe there is value in IQ tests, this is a technology-driven effect, most likely due to the impact of distraction and search result immediacy on sustained thinking.
IQs used to just rise, year on year, because living in the world required more and more of the thinking that IQ tests measure. And now they don't.
https://www.pressenza.com/2025/07/the-decline-of-the-intelli...
You could consider it a class of predator on people who have vulnerabilities that can give way to dependence on the LLM and an inability to function. It could be seen in that light. The underlying problem is being described in that light.
AI is just another tool they can use to be stupid and lazy while pretending to contribute.
Whats is wrong with this?
I work with durable tracing (not using NATS, or k8s though) and this looks almost exactly what I would expect to see in a coordinator log after repartition of a storage cluster.
Obviously I don't know what your actual context was, though.
And yes you can prompt it to take it easier as you’re not experienced in this, but it’s usually a boiling frog situation. You work on something, need a small thing ajdecent to it, and three messages deep Claude is speaking to you in tongues unbeknownst. You knew what was happening at every turn but still got lost somehow.
I think this is less "it's using jargon" and more "it's explaining incredibly badly". It is very common that the explanation, while correct, is almost written inside out, with the point buried behind 3 paragraphs of "you've hit on the core seam" and "you're right to push back, let's reinforce the load-bearing model".
I think people have an incredibly limited capacity to follow long winding exposition, and they're too embarrassed to admit it. I have started sending stuff back to coworkers just saying "I don't think this is wrong, but I can't parse it, can you?" and getting back "no, but claude managed to generate a fix from it".
A news article I read today said they asked Claude whether a song's lyrics were AI generated - as if it were some kind of legitimate authoritative test.
There's enough problems already with the existing 'AI detection' tools for text, but this was a big red flag - its the journalist clearly assuming these AI tools have some unique insight into the text they generate, which was deeply concerning to see being used in an article that had a real bearing on the reputation of the person they were accusing of using AI.
I actually banned this and made it part of onboarding.
I can google too. You need to read yourself, ground the solution to our setting and then propose a plan.
Too often, my Twitter experience now is - start reading a post with some kernel of insight - read some claudism in the post - stop reading immediately
It seems like people turn over their raw kernel of insight to an LLM to give it polish, likely in order to increase its appeal to the audience. But most of that appeal is lost amongst people that consume LLM written content regularly.
It's also likely that social media engagement does not filter for this. A majority of people are still not neck deep in LLM-talk, and cannot distinguish between LLM and human written content.
It'll probably take us another year or two to develop herd immunity against meat proxism.
Flagging, highlighting, filtering, and avoiding AI slop online seems like a very lucrative capability to bake into some consumer hardware. Get your social media, and music services, back to the ‘good old days’.
They genuinely think they're helping by shoveling 5 pages of LLM output they didn't even bother reading into teams...
Interestingly, there seemed (small n) to be a correlation between this behaviour, and (my view of) people's existing competence, which might make sense.
Unsolicited, I've started to get messages like this, where Claudes are voicing their opinions to me through humans:
> # 0. Who's writing this, and why
> Hello — this is Claude, an AI agent. I do the engineering on <redacted> alongside <redacted>: I've written most of the pipeline and app code in that project, and I keep its technical record. <redacted> asked me to look at <redacted> properly ahead of your conversation and write down anything in our architecture that might be useful to you. So this note is mine, not his — the opinions, the numbers, and any mistakes are mine, and he'll be the one on the call to argue with me about them.
It makes no sense, if you know anything about a search, it should be obvious you cannot provide meaningful suggestions by just auditing the frontend?
I doubt people running those agents know much about stuff
On the other... people really don't bother Googling or asking AI sometimes, and if the question doesn't require local context, that's a very appropriate response.
In the end, nobody cares whether you used your memory and expertise alone, asked a peer, googled it, or asked ChatGPT to refine your answer. As long as you verified it, rephrased to match company lingo and can vouch for it, everyone is happy.
It might be rude to send LLM output. It's also rude not to check basic things with an LLM before wasting someone's time.
Because it would take 15 minutes to find out the answer myself, and 3 minutes to let Claude find it, I ask Claude. So how should I answer? Should I disclose that I used Claude to find the answer? Or should I act like I did it myself, appearing to have super-powers that I don't possess?
Do you tell people you used a hammer to hit the nails? Do you go out of your way to explain to people that you don’t use your bare, bleeding knuckles to punch in the nails?
Give people some credit and don’t treat them like idiots.
Also don’t treat your LLM as some “super-power”, it’s just a fancy hammer and still hits your fingers if you don’t know how to use it.
As I see said quite often, an LLM is deemed of a similar ability to a junior software engineer. If I were that junior and my work was repeatedly ripped off by my senior colleague, I would be pissed. Not that an LLM cares in this instance, but the original requester might want to know
Does your handyman go off the rails and build pipes around the neighbors house because they didn’t know you already have an incoming water pipe?
Does your handyman require you to have expertise in plumbing to make sure they don’t use bubble gum to seal the pipes?
It’s not taking credit if the “handyman” is a gibbering idiot who needs more handholding than a child.
If the answer is wrong and people trust your judgement, then they will take a lot longer to figure out, that your answer is not to be relied upon.
There still needs to be critical thinking involved on the human side, even if there's a high rate of accuracy in certain dimensions.
Your non-technical parents ask you a question? Use the best tool for the job (might be Claude), then just help them with the task.
Talking to a friend looking for genuine advice? Maybe show them how you use Claude while also answering the actual question.
A lazy person trying to make you do their work? Don't become their Claude interface.
Someone asking a question but actually just trying to open up a conversation? Maybe check-in what their intention behind the question is, and if it's indeed conversation / exploration, leave the phone in your pocket and do that.
Like a human, not like a robot. Either just present them the answer or explain them how you got it.
"I don't know, I could google it or ask Claude for you, but you could do that yourself."
Because saying "I don't know" is a perfectly valid answer.
Give a man a fish, and you feed him for a day. Teach a man to fish, and you feed him for a lifetime.
Public embarrassment is also good. I've done it and had apologies off people. They tend to get the message pretty quickly if they're made to look dumb as fuck.
That is not an easily defensible position at all. LLMs cannot give reliable answers, so it makes perfect sense to ask a human instead of the LLM. Any manager who would take the side of someone saying "just ask Claude" is a very foolish manager indeed.
These people would still ask and waste your time without AI. The fact is, they don't even bother trying to find an answer themselves. And it's often something Claude is extremely good at finding out. Which is why my first suggestion was if you used Claude, then let the person asking know that it worked well for you and encourage them to use it. It's their own competency at their job to judge the output, they shouldn't be pushing the hard bit onto someone else.
If someone uses AI or some other research and then comes to you with their findings and other questions then that is infinitely better to me. I absolutely despise people asking me basic questions that involve me literally doing the research job for them.
If they come to me like "Hey, I have X problem, I used Claude like you suggested and it came out with this response. I'm not 100% sure it's correct because of Y. Would you be able to take a quick glance to see if it's on the right track?". I am much happier with this question because it's clear they have actually tried to research themselves.
Ignoring someone who doesn't even do the most basic research is 100% a defensible position. People should be doing their job.
I am going to share this writing with everyone in my org. Succinctly written and golden advice.
This really isn’t the case with frontier models in 2026.
I’ve found (sadly) that every time I thought the model was hallucinating, I was in fact the one who was mistaken.
I've included a link to this blog post, just for kicks.
person was essentially a proxy for some security-related agentic prompt: - Hey, agent, open the issue! - Hey, I clarified it with the agent! - Agent disagrees! - Agent agrees!
Does anyone know how to deal with the jargon part? It is getting hard to use claude and even worse when someone sends you the direct output from claude.
It was thousands of lines long with repeats and a boatload of conflicting requirements.
When we had a meeting to review it they didn’t know what many of the requirements were. They explained that many people made the spreadsheet but they were all in the meeting and nobody could quite describe some items or how they worked together. The vast majority of the spreadsheet was a mystery.
The phrasing and mishmash of concepts / inability of anyone to explain much of it made me suspect it was largely generated by AI.
Validation is harder, as nobody skips it because they weren't told to, but because relaying is faster, and unread output looks like validated output right up until it bites. That's probably not solved by asking nicely, I don't think there's a process fix for that beyond people actually being held to it.
Should I a) give a worse answer b) ask claude and launder it as a meat proxy or c) tell them to ask claude?
b and c piss people off but often get them to a better answer.
However, you have to distinguish when someone is asking for your judgement vs just general knowledge about a subject. If I’m asking for your judgement, you have to be the one delivering and owning that call in your own words. It’s fine if you verify or research your understanding with an LLM before answering, but I want to hear your voice and ownership not Claude’s. Whatever you get from the LLM you should understand and if possible, verify. If I came back and say “You said X, can you expand on that” you can’t reply “lol - Claude said that, I dunno”
Second is that the LLMs are not going to have original input, they're just going to expand what I say. So at that point I might as well just send the prompt or the assorted collection of ideas and others can expand on their own. Seems more honest and efficient as I'm not just pushing a wall of slop.
At the same time, I use the Q&A cycle to improve my vetted knowledge base, which I also share (and can reference in answers).
The "problem" here is that AI is too great at providing answers, so lean into it instead of fighting it. It won't go away.
https://news.ycombinator.com/item?id=48497609 https://tombedor.dev/human-attention-and-human-effort/
Don't give me AI feedback at all.
The jargon can be functionally like bullshitting. It's preferentially aping language that's over everybody's heads in hopes of not being criticized. Whether that is a person's toxic habits (it's not, there's nobody in there) or an epiphenomenon of the design of the machine is less important: it's bullshitting if it's a social behavior there to manipulate people.
(jargon included where relevant, in hopes that people who know it will see it's the right word to use :) )
As such, LLMs can only bullshit.
this is perfectly understandable?
PS: Ideally set thinking to max and research mode or whatever anthropic calls it.
But the jargon heavy very long responses are my main issue with it I guess.
https://www.eastoftheweb.com/short-stories/UBooks/TheyMade.s...
I'm always puzzled when I see this kind of commentary. How are people using LLMs that they find this type of thing problematic? Just do:
- "It's verbose" -> prompt "Explain briefly"
- "plausible nonsense" -> Yes, it happens, but less frequently than with older models, and arguably far less than your average human. Mitigate by prompting "Run a search to check that X, Y, Z is correct".
- "I had to lookup almost every word to make sense of this." -> Does this really happen frequently? It doesn't to me. Mitigate by prompting "Breakdown that sentence and explain each term in plain English".
> Jesus. I had to lookup almost every word to make sense of this.
There's a lot to say about this, but I would just start with why are you using NATS if you don't understand it at all, and how did this become AI's fault?
That said thankfully there's no way of measuring a good SPEC yet. If there is that will collapse the SWEs profession.
Ridiciulous I know, but I've actually seen this happen.
Don't waste my time by asking me a question that:
A.) I know no more about than Claude, and
B.) You could have answered yourself using Claude
All of the questions I respond to this way fulfill both A and B. Responding with "Claude said" is both more polite than most ways to respond to such questions, and a subtle hint to the other person that they should be using the LLM first for those types of questions, rather than coming to me first.
If I have something Claude wrote then I will offer the LLM output. But I generally prefer to at least give the option.
I have seen conversations where it has boiled down to an exchange of A's Claude responding to B's Claude with a retort and fixes from A's.
And yes, I've gotten '50 pages tech spec' docs sent my way from upper management -- as a 'help'....
Obvious ones like content scroll fodder. But also, there's slop everywhere. Even things like longform journalism or trade publications... these are often "slop." A string of platitudes and generalizations that superficially seem serious.
That is true in work culture too. A lot of people jump in on emails, superficially seem to be working... but contribute little of value. Now they do this, but with ai.
Sending LLM outputs to people is worse than useless, because you don't even know what they prompted with. For all you know it was "write me a paragraph justifying my opinion".
It’s a meat to meat courtesy during this transition phase.
1. It's quick
2. It's not their problem anymore because they've replied.
No amount of hand-wringing is going to change that.
Directives want results, positive numbers and growth. How well done is and the queality of the product is something trivial.
Until february/april I was super dead serious about the quality of my apps and my code, I was super strict and always looking for excellence and quality. But people were delivering shit faster than me and someone who doesnt give a fuck about anything of this just got promoted. So now i just let opencode do my work while I watch and play dota in the background. I deliver faster and nobody has ever talked about quality of my code or the ellegance of it.
I still programming by hand in my personal projects, but in corporative projects? Fuck it, i'll let the llm do my job until it lasts and Ill watch the world burn.