Comment Re: I use Pacific C Compiler (Score 1) 257
I would modify this advice slightly by suggesting you print out the documentation and get it professionally bound. In fact print out multiple copies. Document (and print) all the details of the development and maintenance processes. Everything from electrical schematics and tolerances to specific compiler versions.
Take the time to paginate all of the documentation and then build indices. When referencing code modules give printed hash values so potential bit rot can be detected.
I have CD-Rs, hard drives, and floppy disks that are twenty years old and can no longer be read reliably. However I have forty year old technical documentation that I can read with no issues.