Following on from Five Truths about software development III[^]
1. When you've checked in all your code and feel all smug as you wait for the rest of the team to finish their work for the sprint, you realise that 6 new bugs have been raised needing your attention before the software can be released. Suddenly you're the bottleneck.
2. When the only estimate you can give to the project manager is "How long is a piece of string".
3. The terror you feel when you have to upgrade your development environment in case it breaks something.
4. Triple checking the question you're about to post on Stackoverflow as you just know there's going to be some smart asses who wil pick your question apart or just plain downvote it.
5. The buzz you feel when you finally fix that bug that's been evading you for days![Big Grin | :-D]()
1. When you've checked in all your code and feel all smug as you wait for the rest of the team to finish their work for the sprint, you realise that 6 new bugs have been raised needing your attention before the software can be released. Suddenly you're the bottleneck.
2. When the only estimate you can give to the project manager is "How long is a piece of string".
3. The terror you feel when you have to upgrade your development environment in case it breaks something.
4. Triple checking the question you're about to post on Stackoverflow as you just know there's going to be some smart asses who wil pick your question apart or just plain downvote it.
5. The buzz you feel when you finally fix that bug that's been evading you for days
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
Home | LinkedIn | Google+ | Twitter