You've only added two lines – why did that take two days?
An alternative take to this article would be that this person wasted two days because he was reluctant to ask more questions from the person who filed the bug report.<p>How often do you actually receive quality bug reports at work? My experience is that external or internal users almost never provide sufficient information and you as a coder are always expected to drill down on what they reported with a barrage of questions.<p>ie. if you are not doing <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Five_whys" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Five_whys</a> then you might be doing it wrong and wasting time because of it.<p>I&#x27;m referring to this:<p>&gt; Some developers would have immediately gone back to the person reporting the problem and required more information before investigating. I try and do as much as I can with the information provided.<p>Which seems like being stubborn and making a mistake because of it.<p>Couple other parts also seem a bit overdoing it:<p>&gt; Because I investigated if there were other ways of getting to the same problem, not just the reported reproduction steps.
&gt; Because I took the time to verify if there were other parts of the code that might be affected in similar ways.<p>These seem like taking a gamble. Maybe something comes up, but is it more probable that this work should be minimised until there is more proof of &quot;other ways of getting to the same problem&quot;? Developer time is expensive, is this really the best way of using it? Would it make sense to just fix the issue at hand and only put in more time if more bug reports come in after the fix or if there is some other indication that this part of the code might be more broken?