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.
We fall in love lust with the outer appearances of some newfangled technology.
We have a great time with all the new experiences and cool things we do together.
We sprint into a committed relationship.
Then we start to spend "resources" (time and money) on dependencies, tool upgrades, etc.
Any formal training is either non-existent or too expensive.
We start to formalize procedures and policies.
Then we get completely married to the technology even though we are starting to have doubts.
Child applications show up and the software gets more complicated and interdependent.
Soon after, we meet some new technology and have an affair.
Next, we're heading to divorce court.
It's that some of them, for a short while, thought it would be best to get rid of IT and use outside contractors. Someone, in the background, reawakened them to the facts that not only does our stuff work better, but we're more responsive to changes. And they have their face in our stuff almost all day long, keeping the company running.
It's like the the old Chinese fable about the body rebelling against the stomach because they didn't think it contributed to the person - so they stopped feeding it . . . .
Scrubbing all propriety and confidential information
So we are involved in various testing of prototype tools ( costly and all info/ datasheet not available) and time was the essence to maintain the deadline and enough pressure from people above my pay grade. The corresponding SME from product team was on vacation and not returning for next 2 weeks and my manager was vacation too. So yours truly proceeded with the test setup and execution with the knowledge I had .Was say 99.99% sure that I am doing right. I emailed my manager with my reason for starting the test and risk if I messed up.
Well to cut the long story short, the electronics in tool got destroyed as I was not in loop in recent changes in the power module. So per policy , we had a Fact finding meeting ( Whom to blame and dry his skin meeting). I presented the sequence and why tool got destroyed. So they asked me, why did I start the test with SME out of town blah, blah. Deadline cannot be a reason for not waiting etc.. Then my Manager interrupted and said verbatim ,
I approved the execution of the test and he had informed of the risk but I said , Go ahead. And please don't even dare ask me why I approved the test. In this same Room two weeks back, some of you and others lamented that Departments are slacking and often come with vacation and lack of engineers excuses for not doing the job. Mr X few minutes ago lectured on that Deadline is not a valid reason but two weeks ago you said Deadline cannot be compromised for any reason. You asked us to be proactive and take initiative and get the job done. Failure will happen sometime but you said it is part of the learning curve while changing our way of doing things here. So Please, I have real work to do and I would prefer if this meeting sticks to fact finding and lesson learnt. So My humble request is please give the engineers due respect for doing the job and lets keep the management insights away from them. My department task always has some risk and that's the cost of doing business. We would mess up once in a while when we are doing our job but don't blame us for that. Take us to cleaners for not trying but don't ever complain that we are trying too hard.
So Should we order pizza for all of us if we are going to stay longer?"
Too much of good is bad,mix some evil in it
I'm a little jealous of your position, I worked for a similar manager once but he was run out by follow employees because he held them to high standards and expected them to answer for not doing their job.
He understood that mistakes happen, but so long as I had acted on the best information that was available to me at the time then he'd support me. Never gave a reason for him to have to stand up and defend me, although I'm sure he would have.
Now I get chastised for defending myself when things go wrong.