Seven Habits of Highly Effective Unix Admins 136
jfruh writes: "Being a Unix or Linux admin tends to be an odd kind of job: you often spend much of your workday on your own, with lots of time when you don't have a specific pressing task, punctuated by moments of panic where you need to do something very important right away. Sandra Henry-Stocker, a veteran sysadmin, offers suggestions on how to structure your professional life if you're in this job. Her advice includes setting priorities, knowing your tools, and providing explanations to the co-workers whom you help."
What habits have you found effective for system administration?
Re:Bait (Score:4, Interesting)
From TFS, I really don't get why that applies only to Unix admins. That describes the years I've spent as a Windows admin as well.
To be an effective admin AND stay in a job (Score:5, Interesting)
Rule #8 would be not to fix problems too quickly (and let some that you can see coming, happen).
If you fix every problem before it gets serious and avert the other 90%, your bosses will think they have a highly reliable IT infrastructure. They will then cast their eyes about for cost savings - and the biggest target will be the most highly paid admins - the most senior ones - YOU!!!
So keep the problems coming, as all that management have to assess you on are the number of fixes and the time to fix. Nobody ever got promoted for solving problems that never happened.
Finally: 60 hours a week? Don't be daft. If you're really an effective administrator you should have your work finished well inside 30 hours and/or 4 working days.