There's a server in our building, it was bought on a capitol expense for over £8K two years ago.
In that time, its NOT had a single thing put on it... In fact, its had something put on it and then taken off it, and that something was deemed to be mission critical enough to warrant being put onto a PC under a guys desk, with its innards spilled out on the carpet... where anyone could tread on it, cleaners could smack it, and hot drinks could pour into it... This was of course our main source code server.
Today however, after many moons of delay, the server is being put back into the server room... But its all changing...
Now, its time for me to say it, CHANGE FOR CHANGE SAKE.
The remit was to get the server back on the heavy iron in as fast and easy a method as possible... Happily the actual machine is really three virtual machines being hosted on this little gutted PC... So one would assume that to get the server back up and running as fast as possible the easiest thing to do would be to stop the virtual machines, back them up, copy them to the heavy iron and start them again?...
Yes... NO....
Clearly this was too complex a task, so instead the appointed administrator, who lets face it has failed to administrate for over a year, has decided to spend the day kicking about in the kitty litter of the interwebs, changing how the server works, how it appears on the network, how you log onto it, and hence how all the services built up over the last eight-ish years using it operate.
The net result is a server which does not work, the invalidation of about 3 months work of mine, and the seemingly unbounded immeasurable incompetance of said administrator being left unchecked as it spews through evolution after evolution of server infrastructure.
The reason for this big problem?... The actual IT Dude doesn't want to learn "sudo shutdown -r now".. That's pretty much the ONLY reason for this change which has had such drastic, terminal, effect.
So people DO NOT just change things for change's sake... and managers, when your fuck-tard employee who has failed to migrate the server for over a year decides you've actually noticed and they tell you "I have a cunning plan sir", don't listen to the smegger, go through their plan with a fine tooth comb, run it past the actual users of the machine and if its going to cause them grief get the fuck-tard to change their plan...
"I asked him to migrate it in as simple a fashion as possible"...
"Yeah, well he's fucked that up royally, I'll go back to zipping up the source code and storing it on a fucking floppy disk each night".
No comments:
Post a Comment