I've been working on an client project for a few months now, and all this time we tested the code as much as we could, by myself and the client, and unit test coverage was quite high.
Software is working as expected, client is happy and we are ready to go live. Suddenly, a mayor bug. Bug that can't be ignored! Do you take it a an inconvenience that should turn your stomach around, or do you take is as an opportunity to improve the software? It is after all, your work, you are responsible for it, you should feel anxious when this happens, shouldn't you? It's an uncomfortable feeling.
In that moment instead of negative look on it, I've tried to take a positive attitude. This looks like a perfect opportunity to revisit feature, where bug is occurring and improve it, and also, fix that darn bug. How often do you have that amount of motivation to revisit and improve code from the past, feature that you thought is done and ready to blast? Let me tell you, there is not better motivation then a crucial bug in your code, code that needs to go live in a few days...
I have rewritten feature, as I did not like how me from the past have done it, and in the end, code size was smaller, less coupled and database contracts were simplified and more fluid.
Depending on how you set your mind on a it, a problem can be a great opportunity, not the inconvenience.
Top comments (0)