Ever. Just don't do it.
I head to a client's site. In order to connect to their domain I have to let a sysAdmin f*ck with my machine.
Alarm bells go off, but I let the monkey have his banana.
To cut a long story short: it's the next day, many hours of work have been lost. Much frustration has been achieved. And I have a new rule:
No f*cking sys admin is touching this machine, ever.
It's the thin edge of the wedge. We let sysAdmin's screw with our machines today. What's next? Database administrators messing with our databases?
'secretGeek' on Thu, 17 Jun 2004 03:41:28 GMT, writes:
i like your way of thinking sandeman...
just evil enough
URL: http://secretGeek.net
'SanDaemon' on Wed, 16 Jun 2004 23:46:01 GMT, writes:
Having been a DuhveLoper and
Admin Is Trator in the past my self I five you this piece of advise.
If you give the monkey a bannana he will eat it. Let the invasive local help you F*** up the office managers favorite system. Then write your code in the quite bliss of one less monkey.
URL: http://www.Sandeman.com
'secretGeek' on Tue, 01 Jun 2004 23:19:30 GMT, writes:
brilliant idea Meski!!
URL: http://secretGeek.net
'Meski' on Tue, 01 Jun 2004 22:42:17 GMT, writes:
Fine, let the sysadmin on your machine - but only as a locked-down user. :) Boot's on the other foot now, mr DomainAdmin! :>
secretGeek .:dotnuts about dotnet:.
Alan Kay on 'The Camel has Two Humps'
The Best Software Writing I
The Business Of Software (Eric Sink)
bookmark at Del.icio.us!
reddit this