4 ms·
> which lets me make forward progress on deduction before I forget WHY I was looking under this rock in the first place. There's nothing quite as deflating as
by kbenson 10y ago
> which lets me make forward progress on deduction before I forget WHY I was looking under this rock in the first place.
There's nothing quite as deflating as finally getting to the end of diagnosing a particularly pernicious bug just to have the understanding trigger the realization that you've encountered this bug before a year or two prior, spent just as much time originally figuring it out, and had somehow forgotten about it the interim. Yay for wasted days of our lives.
- erikpukinskis 10y agoWhenever I unravel a hard-to-diagnose bug, my first step is always to put a better error message in the place where it would have been properly diagnosed.
- kbenson 10y agoSure. I can't recall the last bug that brought this feeling (sigh, the circle continues), but I vaguely recall it being a weird interaction or behavior when interacting with some remote system, and it wasn't in fixing a bug that popped up, but in implementing a new feature or system that interacted in a similar way, but the prior implementation was either in a different project or had since been discarded. I know that's vague. That probably means I'll encounter this again and not identify it as the same problem. :/ I think I need to make a concerted effort to get more sleep.
- hinkley 10y ago// Increment this number every time you end up here // time spent = 30
- TeMPOraL 10y agoIf you haven't recognized your "old bug friend" during the figuring-out process, maybe the path that lead to the bug was different this time? I.e. you have an old bug in a new context, which is almost like a fresh new bug. Personally, when I find out / solve something tricky I note down the details in a notes file exactly for cases like this. I'm yet to use it though, because I usually remember the weirder bugs I've seen.
- kbenson 10y agoI'm pretty sure it was. From what little I remember of it now, I think it was probably best classed as "weird and esoteric undocumented or wrong behavior in a remote system or API".