<story><title>Mea culpa: How developers fix their own simple bugs differently from other devs</title><url>https://neverworkintheory.org/2021/08/10/developers-fix-their-own-simple-bugs-differently-from-other-developers.html</url></story><parent_chain></parent_chain><comment><author>barrkel</author><text>The less you know about code, the more local your changes. In fact this is how the architecture of a software system degrades: lots of local changes sort of make it &amp;quot;melt&amp;quot;. Global invariants become temporally or spatially local invariants, code and data flow which had a single purpose acquire multiple purposes, names become semantically overloaded, and so on.</text></comment>
<story><title>Mea culpa: How developers fix their own simple bugs differently from other devs</title><url>https://neverworkintheory.org/2021/08/10/developers-fix-their-own-simple-bugs-differently-from-other-developers.html</url></story><parent_chain></parent_chain><comment><author>rembicilious</author><text>When my own code presents a bug I tend to chase it back to it’s “philosophical roots”.&lt;p&gt;I tried to work out edge cases from the beginning; to handle invalid data; to swat the bugs before they appeared.&lt;p&gt;A bug reared it’s little insectoid head.&lt;p&gt;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.&lt;p&gt;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.</text></comment>