|
I never get distracted, I was always looking at the shiny.
Format Success.
Welcome to your new signa&*(gD@@@ ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif) @@@@@@*@x@@
|
|
|
|
|
...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.
|
|
|
|
|
The moral of this story is "vacations are dangerous".
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
No! 'Vacations are short'! I should get back AFTER the errors are handled...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I once had something similar happen. I had to get code done by a certain date.
I completed it with associated tests. All good.
I released it to the team for deployment.
They sat on it due to waiting on another developer.
Finally, weeks later they came to me because my piece would not run in production.
I could not figure out why it wouldn't run.
Finally, I looked at the code and it was nothing I'd ever seen before. I could not figure out who wrote this code, which was supposed to be mine.
Finally, I discovered a Contractor-Genius had rewritten it. I asked him why.
"Your code was wrong," he said.
"Yes", I said, "apparently we could tell it was wrong because it actually runs. Yours however is completely right except one small thing: it doesn't run." 
"Well," he said. "You've got to get it running in production."
|
|
|
|
|
didn't keep a personal backup?
you just restore to that, quick check, and hand it back to them [as you leave for the day].
Format Success.
Welcome to your new signa&*(gD@@@ @@@@@@*@x@@
|
|
|
|
|
Lopatir wrote: you just restore to that, quick check, and hand it back to them
That is exactly how I handled it.
|
|
|
|
|
Time for another vacation! 
|
|
|
|
|
Your coworkers have orked your features?
That's easy:
1) Don't say a word.
2) Give them a long, sad, disappointed and otherwise unreadable look.
3) Turn around and leave for the rest of the day. Don't react to any attempt to communicate. Everything has been said.
4) Return tomorrow with a request for another vacation.
I am endeavoring, ma'am, to construct a mnemonic memory circuit using stone knives and bearskins.
|
|
|
|
|
I think this falls cleanly under the "you break it, you buy it" rule.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Quote: 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
Well, after all, they fixed a problem... 
|
|
|
|
|
One step forward ...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
- Send the meeting summary to the PM responsible for the product
- Send the results of the current test run (half of all features ruined) to the same person
- Duck
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
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.
|
|
|
|
|
Marc Clifton wrote: Followed by a slow decline in productivity, years of lethargy, and a sudden interest in other more rewarding activities.
You forgot losing the will to live somewhere along that road.
I am endeavoring, ma'am, to construct a mnemonic memory circuit using stone knives and bearskins.
|
|
|
|
|
The path to self-discovery is rarely an easy one to traverse. 
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
It was more the path to self destruction.
I am endeavoring, ma'am, to construct a mnemonic memory circuit using stone knives and bearskins.
|
|
|
|
|
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.
|
|
|
|
|
I once had a boss (former coder--always a bad combination) who had been hounding me for months to implement a feature that I had explained was pretty much going to require someone full-time to maintain because it was going to have to work with constantly changing data.
One weekend he wrote the "feature" himself and bragged about it to me on Monday morning. It's one of those features that worked on his system, but pretty much nowhere else--ever. Lets just say that it worked okay for 0.000001% of the data it had to work with.
Then the feature became a bullet point in the marketing material. Fortunately it became apparent that nobody but him actually cared, because in the end nobody bought the product because of the feature (or else everybody would've complained it didn't work).
|
|
|
|
|
Everything depends from the situation, so I have many ways to calm myself - reading, screaming or just deap breath
|
|
|
|
|
You write stuff. Some idiot breaks it. You get paid to fix it. Repeat ad infinitum.
Dispiriting, maybe, but if there weren't so many human wrecking balls in the IT trade, there wouldn't be all that many jobs in the IT trade. The bottom line? WE NEED BAD DEVELOPERS!
98.4% of statistics are made up on the spot.
|
|
|
|
|
It sucks when people just go ahead and do that - if you work in IT long enough it's bound to happen.
I would just say make it clear to them that they get to clear up the mess as they acted against your advice and when you weren't there.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
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. 
|
|
|
|
|
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.
|
|
|
|
|
Think of a happy thought, nothing's constant.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
