The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions. Or if you must, use the Back Room[^] - but enter at your own risk.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen. For those discussions where you wish to be a little more frank, use the Soapbox[^]
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
...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.
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."
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 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).
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.”