|
If developers are solely responsible for finding bugs, your company is doing it wrong. Don't feel bad, our company is also doing it wrong; not having a QA department is a rampant cost saving measure. I'm not sure I would try to feel less guilty about having bugs, that guilt helps you be conscious about finding them before going to production. Keep in mind it should never be solely your responsibility. If you don't have a QA team, you should feel less guilty, because the biz doesn't think it's important to hire at least one QA person. If you don't do user beta testing in your cycle, you should feel less guilty, because the biz doesn't think it's important to establish that communication relationship. I work as an internal dev environment now, but I have worked at several software companies that sold software to other companies, and they were pretty mission critical to the clients. We had a dedicated and talented QA department, we had automated testing, and we had a beta cycle with a few choice companies to help us find bugs. Bugs still happened but we took measures to make sure they were minimal if they ever got to a release. Try to minimize the impact of a bug. In the example of the user losing an hour's worth of work, perhaps save periodically. Also, any bug you squash, particularly in production, you should make a script and make sure that gets tested every time. Unit tests are great for this. Definitely keep being a perfectionist and honor your craft, it will pay in spades throughout your career, especially once you get older. |