undefined | Better HN

0 pointswhynotminot2mo ago0 comments

Yeah. Everyone sort of assumes that not having personally written the code means they can’t debug it.

When is the last time you had an on call blow up that was actually your code?

Not that I’m some savant of code writing — but for me, pretty much never. It’s always something I’ve never touched that blows up on my Saturday night when I’m on call. Turns out it doesn’t really change much if it’s Sam who wrote it … or Claude.

0 comments

croes2mo ago

The problem is you lose abilities if stop writing code completely.

There is a difference between a lector and an author

geetee2mo ago

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

whynotminotOP2mo ago

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.

geetee2mo ago

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.

whynotminotOP2mo ago

> 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.

crazygringo2mo ago

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

geetee2mo ago

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

crazygringo2mo ago

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.

j / k navigate · click thread line to collapse

0 comments

croes2mo ago

The problem is you lose abilities if stop writing code completely.

There is a difference between a lector and an author

geetee2mo ago

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

whynotminotOP2mo ago

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.

geetee2mo ago

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.

whynotminotOP2mo ago

> 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.

crazygringo2mo ago

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

geetee2mo ago

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

crazygringo2mo ago

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.

j / k navigate · click thread line to collapse