3 ms·
I think the last point is the best one, and something that I'll try to keep in mind > And what do you do when that awful, black day arrives? Here’s a quic
by douche 11y ago
I think the last point is the best one, and something that I'll try to keep in mind
>
And what do you do when that awful, black day arrives? Here’s a quick coping manual from those of us who have been there:
Don’t pretend it didn’t happen — you screwed up, but your mother still loves you
Don’t minimize the problem, shrug it off or otherwise make light of it — this is serious business, and your colleagues take it seriously
If someone spent time debugging your bug, thank them
If someone was inconvenienced by your bug, apologize to them
Take responsibility for your bug — don’t bother to blame other subsystems, the inherent complexity of the software, your code reviewers, your testers, the community, etc.
If it was caught before it was running in production, be thankful that a production user wasn’t affected by it
- Plishar 11y agoReally? This is all second nature, stuff you should already be doing. Replace "bug" with defect and it can apply to anything. If you find computer work is stressing you out, maybe find a better job that suits your interests?