The 5 Whys of this Tuesday revolved around the typo I made that brought down the forms when we did our last upload.
The "5 Whys" are a session we have during staff meetings to discuss things that have gone wrong during the week, but more specifically why it went wrong. There were a couple earlier on when Mike and I started, so I knew it wouldn't be the whole team tearing me apart.
They've built it as a very constructive session in which they analyze what went wrong midst the team as a whole for errors to occur.
In my case, there were three code reviews, two very specifically on the line with the typo. There was testing that occurred as well.
I've learned a great deal from all of this. The testing and code reviews are in place for a very clear reason. It's important to make sure the testing is all inclusive and that the developer communicates very thoroughly with the code reviewer and the tester. There is a large amount of responsibility on the developer to ensure that every area of the code that they touch will be tested and evaluated.
It's an interesting thing working directly on a product that thousands of people pay to use. Even at Williams, the things my team developed were largely used internally, so if something went wrong, the clients usually didn't suffer
In the end that's all you can ever hope for. To be able to learn from your mistakes and not repeat them down the road.
No comments :
Post a Comment