- backup, archive
- distribute, deploy
- detect which parts need accelerating
- description of erroneous element which disturbes the project workings
- the bits/bytes which take up 90% of the project size, but don't contribute to its inner workings. E.g. image, video and music files.
- information stored to backtrace project activity
- sourcecode which - compiled or interpreted - direct the main project workings
- run commands. Startup configuration files, like for bash, vim, mutt, etc.
- relational database
- statistics of program usage
- vendor (thirdparty, 3dparty, 3party)
- external libraries
- coding standards
- caveats, pitfalls, common mistakes
- functional design
- considerations, justification, purpose, rationale, why, motivation, Design rationale
- MRU (Most Recently Used)
- end-user documentation / manual
- technical documention
- generated documention (from source-code)
Directory: proj/doc/requirements/codingStandards (link)
Layout: rule/why-rationale. Examples:
- Best Practices for XML Internationalization
- W3C guidelines
Rotate log files.
Define how data is archived, and ultimately destroyed.
Of these projects a backup is made less frequently.
Generic-specific or specific-generic?
Often names consist of a generic and a specific part. Should the generic part, or the specific part be named first?
Advantages of naming the generic part first:
- top-down overview
Advantages of naming the specific part first:
- tab-completion is more efficient