One addition to a point of Damian's:
2009/3/20 Damian Brasher <lug@???>:
> 10) Be consistent, be creative (but test creative configuration before
> production), and finally write documentation as you go, it can be a simple as
> you like but will save you lot's of time in the future.
Make use of the tools that are available to you. Use a version control
system to keep copies of vital files when you change them. Use some
kind of note-taking system to capture what you have set up, why, how,
when. 'trac' [1] integrates these two by giving you wiki-type
functionality and a change control mechanism together with integration
with Subversion for source control of your files. 'Elog' [2] is more
just a 'logbook' tool but has nice capabilities.
[1]
http://trac.edgewall.org/
[2]
https://midas.psi.ch/elog/