On Sat, Oct 31, 2009 at 9:16 PM, Ben Rockwood <[email protected]> wrote: > > When I think toward the future, of what we can be and should be > producing, I think the best contribution we can make would be to produce > Best Practice documents and procedures.
This is something I've been thinking about too. I've noticed that Unix systems administration tends to be interpreted uniquely by its practitioners: we're skilled artists, each bringing our own viewpoint and flair. Contrast that to my Windows colleagues, who reach for the manual or best practice document before even thinking about what they're trying to do. (Although I have noticed that their Best Practices tend to revolve around applications, not systems or the OS.) > Even the most experienced administrator wonders, "How are others doing > it?" or "Is this the best way?" And one of the benefits would be a commonality of approach. In our development teams, there's a shared understanding of development methodology - a new developer can be hired and be productive almost immediately as a result. The way that Unix systems tend to be implemented seems to vary far more widely (or I've just been unlucky enough to just get the outliers [and boy have I got some outliers to deal with right now]). > The wiki structure should aid us in > creation of such best practices and procedures. OK, so how to structure it? I can think of creating 3 areas on the wiki: - Final Best Practices - Draft Best Practices - External Best Practices (just links) and once we're happy with a Draft we can move it into the Final stage? > I can't think of any better gift we could provide the community than > serving as a definitive authority on best practice. Not only because we > have so many experts, but because we could become a magnet to attack others. Attack or attract? -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ _______________________________________________ sysadmin-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
