# Beyond README
       
       2018.03.23/11:00
                           ... written by lambda
       
       I'm interested in organizing i.e. keeping my $FUDGE together
       while working.  For me, this is a crucial task, because
       while working, I'm in a deep-trance and thus rather
       concentrated and unflexible.  Sometimes I loose completely
       track of time and space.
       
       I often choose one task and stay on track 'til it is
       finished. If someone would hire me to build a train system,
       it would very probably become a proverbial monorail...
       literally. It would have only one single track.
       
       It would be very cost efficient, very clear, very easy to
       maintain and to copy, and very reliable for shipping only
       one special product, like, i.e. screws or tea leaves...  or
       monorails.
       
       Nevertheless I need to have some pattern to return to,
       because, in the end, even the need to work on a feature
       branch B could become a nuisance while working on banch A.
       
       So I turned to note taking and the use of commonplace file
       names for quick orientation and as a point of reference for
       other as well. Nothing new. This is as it should be.
       
       The following is my small list of commonplace file names
       beyond the proverbial README, that helped me.
       
       While working on a project, I tend to put them all in a
       directory called 'README.d/' and browse it using lynx(1).
       
       
       ## Common Filenames
       
       README     Content description, contact information.
       BUGS       List of bugs.
       CREDITS    List of contributors.
       LICENSE    The project's license.
       TODO       Stuff to do.
       UPGRADING  How to upgrade.
       HACK       Guidelines for code modifications.