On Aug 15, 2007, at 6:27 PM, Andrew Lentvorski wrote:
Then I call you an idiot. And not for the reason you think.
And I, in return, call you a jackass. :D
In the case that was originally cited, this was a technician in assembly in *production*. Time on line *matters*.
In my experience as a sysadmin, people tend to get testy when you're not at your desk and there's a problem. Randomly being out, for anywhere between 5-15 minutes, several times a day, usually means that calls don't get answered, or they come to me, instead.
I really don't like having to do someone else's work. I usually have enough of my own.
Perhaps it's just a particular person I've had to work with before, but every single time we couldn't find him, he was "out on a smoke break." Which seemed to be every single time we needed to find him.
And, believe it or not, some jobs really are 9-5 (or 8-4). The rest of our coworkers, who are there during those normal business hours, don't give a rat's ass how we get the work done if we're not there during the day when they need us.
In the case of more creative work (engineering, sysadmin, etc.), time is not a good measure of productivity. Using it as such makes you a idiot.
No, but your customers expect you to be available during certain times, and not being available on a consistent basis makes you seem like an idiot to your customers.
It also feeds the whole "productivity is sitting in the chair" rather than "productivity is getting stuff done" problem that plagues American business.
In my experience, being a sysadmin is primarily a support function to the organization. Support personnel generally DO need to have significant "time in chair", in my experience, in order to provide good support.
Gregory -- Gregory K. Ruiz-Ade <[EMAIL PROTECTED]> OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu
PGP.sig
Description: This is a digitally signed message part
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
