> These are bad bug reports - because they have no stack traces and no context
heh, clever mind hack. kinda reminds me of Tony Horton's "Don't say 'I'm bad at x', say 'I presently struggle with x'".
Love the Spoelsky 'old code is battle tested/refactor instead of rewrite' - but there is one scenario it doesnt catch, though. traumautic events and abusive relationships can warp that old code quite a bit, making it difficult to trust that what youre debugging is actually your code, or whether its a virus. Sometimes you do have to rewrite.
>> "I feel bad."
>> "I am a failure."
>> "Why can't I get anything done?"
> These are bad bug reports - because they have no stack traces and no context
heh, clever mind hack. kinda reminds me of Tony Horton's "Don't say 'I'm bad at x', say 'I presently struggle with x'".
Love the Spoelsky 'old code is battle tested/refactor instead of rewrite' - but there is one scenario it doesnt catch, though. traumautic events and abusive relationships can warp that old code quite a bit, making it difficult to trust that what youre debugging is actually your code, or whether its a virus. Sometimes you do have to rewrite.
This is kind of brilliant. Both the blog post and the idea of managing CBT as a debugging process. There’s some great insights here, e.g.
> As you fix your poverty, you discover the ennui of abundance.
and the idea that the software is running as intended but it was written for urgent needs that are no longer appropriate.
I love this article. Simple way to express things that in hindsight should be obvious and very actionable. Thank you.