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.
while I don't disagree with your statement. There is always the thought that no one, I repeat no one is irreplaceable.
I have been in the room when a SQL DBA said that to a boss. The DBA did not make it back to his chair across the room.
I agree that local in house IT is always the best. It is best for the company, best for the co-workers (who are not in IT) and best for the IT personal who feel like they are part of something. They get more fully vested and the return on investment is huge. But I urge caution whenever you begin to feel too big for your own britches.
To err is human to really mess up you need a computer
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.
Hi all, it struck me yesterday: when I started in IT, we built programs (systems) like we built houses: we planned the layout, had paper documentation on every routine, it took sometimes years to finish and the investment was huge but it was going to last forever. Additions followed the same guidelines if it was allowed by building regulations. It could house everything between 1 - 10 people without major issues.
Today we program like we build cars. We switch systems every 5 years, not because the current car doesn't suit our needs anymore but just because the other one has a keycard to unlock. Basically, it's just a newer version of the same. In a few years, parts will be difficult to find, cost of maintenance grows. For big parcels we need to rent a van and if we see someone with a newer version, we feel outdated.
Part of the problem is that we don't build systems like we do a house or a car: you don't have to be a professional architect to design software, you don't have to follow any building regulations, you aren't liable if the house collapses when you hand over the keys. You don't need to confirm to government legislation like you do with cars, you don't have to have any testing done at all, and test results aren't in any way public; you don't have to do recalls if there is a bug.
Instead, we have idiots throwing together lumps of code they copied from SO and QA, calling that "new software", being surprised when it doesn't do the job, and shipping it well before it's ready to meet arbitrary deadlines.
And until that changes, don't expect me to worry about feeling outdated!
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
Last Visit: 31-Dec-99 18:00 Last Update: 23-Jun-18 21:46