The constraints of a REAL productin environment can be many. It's easy for you "real IT guys" to say he shouldn't have a job, but you've no clue about the constraints he operates under.
I have an active MD and an active OpD above me in my company and regularly have to fight to avoid having our network integrity compromised by simiarly stupid decisions including;
1. Allowing a customer direct access to our SQL server - access to views and/or via web services wasn't acceptable to them. Problem here was our MD is talking to senior procurement managers in the customer company. Thankfully I have a personal friendship with the customer company's IT guy, so when I phoned him we worked it out that a simple web service would suffice;
2. Allowing a vendor to connect critical equipment directly to the net bypassing the firewall
3. Allowing a vendor root access to our domain
The truth is I don't always win the argument, so my environment also had a few stupid and dangerous elements. Another truth is I'd never make the mistake this guy did to ask for help on here. Most of you "real IT guys" haven't got a clue what it can be like in a real production environment, so you just dispense smart ass sarcasm with no other purpose than to inflate your own egos at the expense of the poor guy who, lets face it, must already be under more than enough pressure and humiliation without your contributions
Slashdot Mirror
The constraints of a REAL productin environment can be many. It's easy for you "real IT guys" to say he shouldn't have a job, but you've no clue about the constraints he operates under. I have an active MD and an active OpD above me in my company and regularly have to fight to avoid having our network integrity compromised by simiarly stupid decisions including; 1. Allowing a customer direct access to our SQL server - access to views and/or via web services wasn't acceptable to them. Problem here was our MD is talking to senior procurement managers in the customer company. Thankfully I have a personal friendship with the customer company's IT guy, so when I phoned him we worked it out that a simple web service would suffice; 2. Allowing a vendor to connect critical equipment directly to the net bypassing the firewall 3. Allowing a vendor root access to our domain The truth is I don't always win the argument, so my environment also had a few stupid and dangerous elements. Another truth is I'd never make the mistake this guy did to ask for help on here. Most of you "real IT guys" haven't got a clue what it can be like in a real production environment, so you just dispense smart ass sarcasm with no other purpose than to inflate your own egos at the expense of the poor guy who, lets face it, must already be under more than enough pressure and humiliation without your contributions