How you calm yourself down...
-
...when you realize, that a new feature has been added to the application while you were on vacation and it ruined half of the existing features... (add to it, that you had a nice meeting about that feature and you mentioned 3 pitfalls of the implementation - of them 2 weren't resolved)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Kornfeld Eliyahu Peter wrote:
that a new feature has been added to the application while you were on vacation and it ruined half of the existing features
I call that epic team work and communication....not. Good luck with that. Been there so many times, I can't feel the pain. :)
-
This is one of those learning moments. The one where you learn "it's just a job, I am emotionally detached from it." Followed by a slow decline in productivity, years of lethargy, and a sudden interest in other more rewarding activities. :)
Latest Article - Class-less Coding - Minimalist C# and Why F# and Function Programming Has Some Advantages Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
You nailed it! That is happening to me. I sent out a requirements document last evening and my mentee/junior went around behind my back this morning, straight to the business unit and contradicted the agreed requirements. And to make things worse, she already started coding; which means I'll end up rewriting it.
-
...when you realize, that a new feature has been added to the application while you were on vacation and it ruined half of the existing features... (add to it, that you had a nice meeting about that feature and you mentioned 3 pitfalls of the implementation - of them 2 weren't resolved)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Or, after a long, and delayed, flight to Europe and a welcome sleep at the hotel, you finally log into your email only to be confronted by a message full of exclamation points that your library is crashing causing the world to end. This is followed by the message, "Never mind, I fixed it." You groan, knowing that said developer is, shall we say, less than knowledgeable. You get back, look at the "fix" and discover it's completely wrong and causes far worse problems (for which you are now blamed.) You check the original bug report and discover the person who filed it is using your API incorrectly. (Then you discover that there was a bug, but it had nothing to do with all the hysteria and, in fact, nobody has actually triggered it.) True story from 1992 at a large, at the time, network company.
-
...when you realize, that a new feature has been added to the application while you were on vacation and it ruined half of the existing features... (add to it, that you had a nice meeting about that feature and you mentioned 3 pitfalls of the implementation - of them 2 weren't resolved)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Think of a happy thought, nothing's constant.
