This is the kind of problem that can be prevented by using "better" coding patterns. Not to say it will be prevented, but that some ways people like to structure code are more prone to these kinds of bugs. I quoted the word "better" because I work with a competent but less experienced guy that tends to write more complex code, or what some claim is just a different style than I would prefer. I make claims that "this…
Let’s be honest this is the kind of thing that can happen to anyone. We all like to think we have picked up habits that immunize us from certain kinds of error but large software systems are complex and bugs happen. The number of people in here taking ‘Raymond Chen tells an anecdote about the time a dumb bug shipped in Windows and was fixed two weeks later’ as an indictment of Microsoft’s engineering culture is frank…
I didn't say I'm immune to doing this myself, nor did I condemn anything about the particular scenario in the blog. My pain is in trying to articulate why some ways are better when any code that works is in some sense just fine.
>> We all like to think we have picked up habits that immunize us from certain kinds of error but large software systems are complex and bugs happen.
We sure do, although "immunize" is too strong. We try to minimize the likelyhood of these kinds of things. Experience is valuable and sometimes it's hard to articulate why.