====== Poor Man's Revision Control ======

  - Create a project folder.
  - Inside the project folder, create a working directory, e.g. //work// (or //erstell// if you live in germany). This folder shall host the files that you are currently working on.
  - Inside the project folder, create a repository directory, e.g. //repo//. Create a copy of your working directory inside the repository directory whenever you think you have completed some important step of work (e.g. implementing an new function, successful running some test, giving away a release copy of your work, or just at the end of the day). Add a prefix to the folder name indicating the release date in ISO format (i.e. work_yyyy-mm-dd) in order to be listed in cronological order when sorted alphabeticaly.
  - It may be a good practice to have a //test// directory inside the project directory. Copy your work from the preository into this directory in order to demonstrate that it can consistently be compiled, build, installed, runned (or whatever) in a place other than the working directory.
  - <del>When you think time is right to release a new version of the file you are morking on in the //work// directory, create an //attic// directory for hosting the previous versions of your file. Move the old file from the project folder into the attic folder and replace it with a coppy from the work folder. Remember to update the date prefix of your file.
</del>

=== Pros: ===

  * The pros of this aproach: no need for any kind of version management tool.
  * Approach available everywhere and everytime.
 
=== Cons: ===

  * Approach needs some discipline in order to ensure that file in the main directory shall not be touched for editing.