Dana Quinn <[email protected]> writes: > One thing I've talked to my team about is that *some* documentation is > better than *no* documentation. Write *something* down, and then > start evolving it.
Yeah. this is important. I tell people to just paste the contents of their history file. I write a /whole lot/ of /really bad/ documentation just 'cause it's 3AM, I'm sleep deprived and the caffiene is wearing off, I got something to work, but if I don't leave myself clues, there's no way I'll remember what I did the next day. There's plenty of time later to fill it out and make it look good. I think part of the problem is that many people, especially young people, don't grasp this 'something is better than nothing' bit. one of my guys keeps saying "oh, but with a little more work, I could script it" which is great, and correct... that's pretty similar to pasting your history file, at least for a really bad script. but the 'leave me a clue so I can figure out what happened after I wake up' is what I really want. But I think a lot of people feel funny about leaving these notes about "But this isn't the best way to solve the problem" is a common objection. _______________________________________________ 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/
