4 ms·
This is a very well-known phenomena. If you don't feel anything after a bug in your code cost your company lots of money and your team members many days in debu
by Devilboy 14y ago
This is a very well-known phenomena. If you don't feel anything after a bug in your code cost your company lots of money and your team members many days in debugging and fixing it... then you're like nobody I've ever worked with.
- jaylevitt 14y agoReally? My first major software release took the AOL mail system down for 34 hours. My later work kept it up for 8 years. I consider both equal fodder for bragging, self-immolation, and war stories over drinks. I couldn't tell you which taught me more.
- PerryCox 14y agoI think what the previous commenters are trying to say is that you shouldn't be OK with producing lots of bugs. Sure, you can learn a lot when you make a mistake, but you shouldn't be making the same mistakes.
- mayanksinghal 14y agoI think the bragging part of the bug that brings the system down for hours and requires significant efforts in RCA is that the initial work was important and the bug likely to be non-trivial. Non-trivial bugs happen. I will not be proud of small stupid bugs I make but non-trivial bugs, the discovery of which brings sort-of an excitement - that is something I can be proud of.
- vacri 14y agoThat sounds like you feel something about both of those things.
- jaylevitt 14y agoYou're right. I feel sheepish and proud and part of a bigger effort, but I do not feel nothing.
- jaylevitt 14y agoYou're right. I feel sheepish and proud and part of a bigger effort, but I do not feel nothing.