In the fast paced world of application development we deal with many things. Software limitations, lack of standardization in the industry, lack of time, resources, and/or quality. These things (and more) lead to bugged, erroneous or just plain bad applications…
As developers, we hate poor quality and we hate it when our products aren’t up to snuff. Take pride in your craft, do it well and do it right.
So when these problems plague our applications: We want them reported ASAP!
We want to know when things need fixin’! If your kidney started misbehaving, you’d want to be notified right? I mean…it’s a part of YOU! That’s what our code is as developers. It’s a part of us. This is my line of thinking anyway.
But sometimes it can be a bit overwhelming. When someone creates something of great value and many people start using it, many bugs can be discovered in a short period of time. This can lead to walking into your office in the morning and noticing you have 200+ e-mails in your inbox. The subject of each one is “HELPPP!!!11!”, and when faced with a wall of urgency and desperation, it can lead to panic!
Seasoned developers have seen these come and go. Under time constraints one has to decide: “What are the real problems?” and “What comes first?”.