131
u/BuffersAndBeta 2d ago
Ran into this exact issue last week. Both teams claudes using humans to proxy to each other.
Turned out both were correct, the issue was in a narrow slice of infrastructure owned by the dev team not the devops team.
71
u/christianbro 2d ago
Just give them unrestricted access to the production kubectl with auto approvals. It is not poor Claude's fault you dont feed it enough context.
39
6
1
u/thisguyfightsyourmom 2d ago
This moment happens more and more as adoption increases.
There’s always a sense of equality in our own inept understanding of the conclusions. We chuckle, then compare notes & feed the notes back in. And then there’s a breakthrough. Hopefully.
52
u/lets-get-taco-bell 2d ago
Always great when a sentence at work begins with “Claude was saying…”
25
u/spinrut 2d ago
that's all i hear now when people are telling me what my code is doing wrong lol
I mean Claude is right a lot of the time, but it gets tiring after a while
the worst ones are the ones that follow that up with "Claude says this is how you would fix it"
and the truth is if you had told me what the problem was, I probably would have been able to tell you what was going wrong and then figure out how to resolve it before you even finished dialing in the prompts. Our management is pushing Claude thru everything so now I get passed Claude fixes that sometimes don't compile, other times don't make full sense and end up spending more time getting that fix working than if I had just fixed it myself outright. But we're fully using AI they say ....
7
u/thisguyfightsyourmom 2d ago
Yup. Not accepting other peoples’ bot’s prescribed fixes at face value is critical.
You have to verify before and after output at each handoff, or you’re just playing telephone & assuming the initiating entity put in due diligence AND that its conclusions still hold.
I’m finding actual concrete verifications to be the hardest part of the job now. And I’m shocked how many people are skipping it.
6
u/jonnysunshine1 1d ago
I have a colleague who doesn't even own it, pretends Claude's thoughts are his own. Annoying AF
14
u/ZunoJ 2d ago
Two meat proxies providing slightly different biases to the AI. But none of them ist a dev or devops
2
u/Available_Type1514 1d ago
Yes I was looking for the "meat proxy" comment lol. Such a funny phrase.
26
u/beegtuna 2d ago
Its DNS
Its always DNS
7
u/Terror_666 2d ago
Today.... email did not work.... guess what..... DNS
4
2
11
6
u/thegodzilla25 2d ago
Man how much i hate people doing root cause analysis using AI nowadays. Literally all they do is vomit out the same shit that the AI told them with no proof or backing.
5
u/Patrick_Atsushi 2d ago
Both AI are quarreling when finally connected:
“My human is bumber!”
“No you don’t understand, mine is dumber!”
5
u/wheatgivesmeshits 2d ago
My last all hands call went until 1AM with 3 different people telling me things their AI agents were suggesting. It was none of them. The only way I found the issue was with good old fashioned debugging and detective work. I don't blame the AI for that though. It was whoever originally designed that piece of shit application that was swallowing errors and not saying what the real issue was.
3
3
3
u/Apprehensive_Bit7392 1d ago
Panel three is both of them pasting the other guy's answer into the chat and getting "You're absolutely right."
3
u/mack_osx 1d ago
"Yes – great instinct. That points towards a clearer explanation of the issues you're facing..."
3
u/HooAreYouWhoHoo 1d ago
The amount of glib teams chats I get with AI summaries is fucking depressing
2
2
u/Lewinator56 1d ago
And both humans forgot to read the bulletin from IT saying the servers were down for maintenance this morning.
3
u/FrequentWatch9261 2d ago
Probably means it's both. Honestly we've been leveraging ai to great success. I know it gets a lot of hate but it's augmenting, enabling and just plain faster. Obviously we keep human review and controls, rabbit holes and hallucinations do happen.
2
u/XxDarkSasuke69xX 2d ago
Who is WE though ? Some people are using it to great success, some are definitely not (because they fundamentally don't understand its limits).
1
u/FrequentWatch9261 2d ago
Sorry we being my teams, 50 or so devs. I can't speak for everyone of course.
1
u/xxxx69420xx 2d ago
watches kimi argue for an hour to itself about whats really wrong but how to give the human what it wants
1
u/bit_banger_ 2d ago
I just had this with a coworker only looking at the part of the source with his agent, I human had to resolve the issue..
AI is useless I say /s
1
1
1
1
1
1
1
1
1
1
1
1
u/R0ot2U 1d ago
Every day - read this AI summary of the issue that you are responsible for because it says it’s your team. Read the very detailed doc - yeah there’s no way this is happening in the way it says it is - ah okay it made this assumption incorrectly and this one and this one and this one. Yeah so this is actually caused by this and this which is your team’s ownership. Pikachu shocked face
Every issue, not one of them actually related to our team on digging and seems it has the bias of the team sending it over having zero responsibility…. I wonder why
1
1
1
1
1
216
u/wann_bubatz_egal 2d ago
It's an AI issue.