491–500 of 786 posts
At my last job, a coworker did this to me. The first time it happened, I ignored it. The second time, I responded in public saying “thanks but I can ask Claude myself.” Nobody ever pasted me an LLM response again. YMMV with team size and seniority though
> frequently contains all too plausible nonsense, and is increasingly jargon dense. 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.
I'm adding "ELI8" (explain like I'm 8 years old) to the end of my prompts a lot. It helps.
Earlier quoted context omitted.
With the recent wave of posts about Claude rewriting entire codebases from Zig/Electron to Rust/Swift, I can't help but question the prompter's actual confidence in the final result. Gaining a thorough understanding of the generated output still demands an enormous amount of effort. I suspect the reality is that most people just chain a few review agents together, and if they output "LGTM", the code gets committed an…
> 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 sing…
We trust them - in large part - because we know that professionals took the care and responsibility to build the foundations correctly.
And if the foundations failed in some way, those same professionals would suffer a hit to their reputation.
I deal with this all day long at work and it’s exhausting. People almost acting like no one has thought of it “I asked Claude what happened, and it spit out this 300 line response. Can you read it for me and see if it’s right?” 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…
Just have devs commit (or provide however you like) their ai coding sessions.
It then becomes obvious if someone has, or has not, reviewed the code, because then they discussed it.
Bonus points: on very complex tasks, you can more or less resume the conversation, via session files.
Same for schoolwork, research papers, and a lot more.
The conversation is not something to throw away: it is arguably as important as the code in the pr.
I deal with this all day long at work and it’s exhausting. People almost acting like no one has thought of it “I asked Claude what happened, and it spit out this 300 line response. Can you read it for me and see if it’s right?” 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…
It’s the equivalent of choosing words from a conversation and sending you the dictionary entries.
I could do that myself. I really didn’t lack the ability to click a button.
I deal with this all day long at work and it’s exhausting. People almost acting like no one has thought of it “I asked Claude what happened, and it spit out this 300 line response. Can you read it for me and see if it’s right?” 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…
LLMs have made G extremely cheap, but verification capacity and judgement has not scaled at anything like the same rate. Someone can generate a bunch of PRs or a report quickly, while transferring hours of verification work to everyone downstream.
We are on the wrong side of this ratio, because we never had the capacity to extinguish reviewer capacity the way we can today.
“Don’t be a meat proxy” needs to be a cultural norm for the larger problem of using cheap generation to externalise verification costs onto someone else.
People get information from Google AI mode and take it as 100% truth. In reality, blogs, reddit, and junk are often sourced link...which is fine if you inspect the sources...which some people don't!
Have has examples of people AI-moding a questing and they get one answer based on how they asked. Then another person asks and they get another answer.
Issue: People read what they want to read, don't listen to humans anymore beacause the AI will tell them what they want.
Earlier quoted context omitted.
The ones who get more productive are either the very incompetent who get pulled up to the AI-floor level, or the very competent who know when and how to use it and for what. The midwits are too proud to use it and instead placate themselves that their precious skill is more special and immune to mechanization than it really is. Many many people have jobs where their contribution is granting access to deliberately und…
I would bet real cash money that many many people, including your coworkers, think that anyone who unironically uses the term "midwit" is completely and totally obnoxious.
I deal with this all day long at work and it’s exhausting. People almost acting like no one has thought of it “I asked Claude what happened, and it spit out this 300 line response. Can you read it for me and see if it’s right?” 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…
The thing I think is so frustrating about this is it's the absolute worst case middle ground between two much more productive experiences. Either solve the problem yourself by understanding the code or just give me the full agent context so I can just use a chatbot too. For high stakes debugging efforts I'll dig in with Claude, have it do a bunch of testing and give me a writeup, and then review it to extract any use…
Consider just using Claude sessions. Claude has hooks you can use to copy local sessions in the repo.
Git LFS can be used to store directly in repo, helping not just with repo size but also with security/privacy/secrets-leaking
I deal with this all day long at work and it’s exhausting. People almost acting like no one has thought of it “I asked Claude what happened, and it spit out this 300 line response. Can you read it for me and see if it’s right?” 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…
At my dayjob there is a person spearheading ai across the enterprise. 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…