[geetee]

"hey coworker, I know your team wrote this, can you help?" Except there is no coworker, just Claude

[whynotminot]

Do you know what on call means?

It means Sam is 7 beers deep on Saturday night since you’re the one on call. He’s not responding to your slack messages.

Claude actually is there though, so that’s kind of nice.

[geetee]

Sam might be 7 beers deep, or maybe he's available. In my org, oncall is just who gets the 2am phone call. They can try to contact anyone else if needed.

Claude is there as long as you're paying,and I hope he doesn't hallucinate an answer.

[whynotminot]

> In my org, oncall is just who gets the 2am phone call. They can *try* to contact anyone else if needed.

Emphasis mine.

> Claude is there as long as you're paying

If you’re at a company that doesn’t pay for AI in the year 2026, you should find a new company.

> and I hope he doesn't hallucinate an answer.

Unlike human coworkers with a 100% success rate, naturally.

[crazygringo]

"Yeah our team wrote it but everyone who built that part of it has moved to different teams or companies since."

[geetee]

Yeah it happens, and it's not ideal, and now instead of a risk, it's a guarantee.

[crazygringo]

Yeah but now you get an LLM to help you understand the code base 100x faster.

Remember, they're not just good for writing code. They're amazing at reading code and explaining to you how the architecture works, the main design decisions, how the files fit together, etc.