zlacker

[return to "War story: the hardest bug I ever debugged"]
1. jonnyc+rs7[view] [source] 2025-03-27 04:02:56
>>jakevo+(OP)
I’m not even close to being on par with other faang engineers but this is far from being a very difficult bug in my experience. The hardest bugs are the ones where the repro takes days to repro. But nonetheless the op’s tenacity is all that matters and I would trust them to solve any of the hard problems Ive faced in the past.
◧◩
2. jakevo+tt7[view] [source] 2025-03-27 04:15:14
>>jonnyc+rs7
Hi, author here! At my job before Google I had to debug these kinds of bugs for our mobile robotics / computer vision stack, but I found them fun so they didn't feel "hard" per se. The most time-consuming one took a month on basically a camera-mounted computer vision system, where after an hour of use the system would start stuttering unusably. But the journey took us through heat throttling on 2009-era gaming laptops, esoteric windows APIs, hardware design, and ultimately distributed queuing. But fixing it was a blast! I learned a ton. I hated that project but fixing that bug was the highlight of it.
◧◩◪
3. Scramb+rw8[view] [source] 2025-03-27 15:01:32
>>jakevo+tt7
I’d read that blog post!
[go to top]