3 ms·
When my own code presents a bug I tend to chase it back to it’s “philosophical roots”. I tried to work out edge cases from the beginning; to handle invalid dat
by rembicilious 5y ago
When my own code presents a bug I tend to chase it back to it’s “philosophical roots”.
I tried to work out edge cases from the beginning; to handle invalid data; to swat the bugs before they appeared.
A bug reared it’s little insectoid head.
Now I’m wading my way through every piece of code that remotely affects the issue and making damn sure that my perfect vision is realised.
On the other hand, fixing a bug in someone else’s code doesn’t have all these personal implications. If I fix the bug without causing regressions I’m a hero! After all, it’s not personal to me.
- cwingrav 5y agoAgreed, and that is the heart of it. - Someone fixing their own code fixes the codebase. Someone fixing someone else's code, generally only knows enough to make a fix at a single point, to fix an observed bug. I think the abstract is just making statistical observations and hopefully in time will develop and test hypothesis that could create a theory. Anyway, they can use my hypothesis above and give it a whirl.