←back to thread

War story: the hardest bug I ever debugged

(www.clientserver.dev)
462 points jakevoytko | 2 comments | 24 Mar 25 14:37 UTC | HN request time: 0.632s | source
Show context
Taniwha ◴[27 Mar 25 11:26 UTC] No.43492456[source]▶
In interviews I've never forced anyone to code, what I do is try to get them to tell me these sorts of war stories - I want to hear how you fixed it, why it was cooly bizarre, and I'm hoping for some enthusiasm when you talk about it.

I couldn't always get people to talk this way, but people who did usually worked out well

replies(1): >>43493025 #
kccqzy ◴[27 Mar 25 12:46 UTC] No.43493025[source]▶
You are selecting for the kind of person who always like to think about the war stories and brag about them.
replies(2): >>43494604 #>>43496830 #
1. AnimalMuppet ◴[27 Mar 25 15:23 UTC] No.43494604[source]▶
No, they're selecting for the kind of person who can tell a war story when asked. They're also selecting for the kind of people who had to debug something gnarly enough and different enough that it was memorable.
replies(1): >>43494964 #
2. kccqzy ◴[27 Mar 25 15:55 UTC] No.43494964[source]▶
Some people are not natural story tellers. Telling a story is not a usual part of the job responsibility of a software engineer—we aren't novelists. Having a memorable debugging experience doesn't directly equate to having a good story to tell.

This is really the same issue with the promo culture we see at Big Tech companies: you end up promoting the people who are good at crafting promo packets i.e. telling stories about their work. There is certainly a good overlap between that and the people who do genuinely good work, but it's not a perfect overlap.

Personally I don't really mind it because I consider myself good at story telling. But as an interviewer I would never do that to a candidate because not everyone can tell good stories.