> My point being-- it's ok, in my opinion, for mistakes to happen (*). > ONCE. Review, learn, manage, prevent further occurrances. A good > boss will apply these rules to juniors too. > > Boy, we could discuss this forever. Time to write a book. > > (*) There is a difficult to describe line between "mistakes happen" and > "this broke because of poor planning". A corollary to the "mistakes > happen" rule in my book is, sysadmins have privileges, and with that > comes great power to wreak great harm. As such, before a sysadmin > (especially a junior) takes action - always always have a > backup/recovery plan. Or two. Or three.
I always try to drill into people (because it seems to be difficult for most) that you must always have a 100% roll back plan, and a clear path as to when you'll do it. To often the ego gets in the way, or the thought, we've invested so much and can't stop. Its not a failure if you roll back properly to try again some other time. _______________________________________________ Discuss mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
