Yesterday we put a project I'd been working on into production, tried it out, and everything seemed to work. I then came back and was sort of basking in the afterglow of putting together something useful and then actually getting to see it in action. I was truly a proud father.
This morning I came in to find that my child had betrayed me and was not working properly. Turned out we'd never verified that it was putting good information into the database! Fixing it was pretty simple and we got everything taken care of without too much difficulty but I felt like an idiot, especially since I had been so proud of it before.
Moral of the story: Pride truly cometh before the fall.
Whenever this sort of thing happens I like to inventory what went wrong and make a 'process' for myself to be sure that I don't do it again. I'm getting a pretty long list now but with each addition I'm improving the quality of my work and that is definitely something to be proud of.
1 comments:
You should have applied your "Three-step program":
1. Unit test your code.
2. Read the list of "Things you should have learned before".
3. Quit writing bugs.
:)
Don't beat yourself too hard about it. "The Dog" is going to sniff trees in a foreign forest, and is not too motivated to sniff yours (Yes, I am speaking in daVinci).
It might be a baby with a wart on her nose, but it is still an intelligent , lovely baby.
Post a Comment