How a good README file is important

In the rush of a day's work with several projects going on in parallel, it is not hard to come across someone asking you for help (support) for something you developed recently, but hasn't make the slightest idea how use this program or utility currently.

I don't know if it happens with you, but with me it happens much. Many times when I do the review of something I had developed and passed a little time without see, I stay surprised with it, sometimes as a positive surprise and others not so much!
Each one do the organization the way it believed to be more productive, but as I usually create many tools for myself and sometimes I share it with other staff members, so it's necessary leave a document for quick reference in templates README [+] and it ends up helping in the process of rescue the subject and even as a user manual.

The content of a README file

In my point of view, a file as this can have anything what is necessary to help in the development and be a good guide for quick reference with use examples and any kind of warnings and tips, someone can say: It isn't productive and have many other tools to do that in the best way and I agree, but here we talk about a little tool and many times a snapshot with a scope more pragmatic of development, so nothing is more quickly and practice than a text file.

Examples of section

  • Header
  • Examples of use
  • Versions
  • Changelog
  • Scope X Solution

Links to the other sites with examples


Comentários

Postagens mais visitadas deste blog

How use the LZMA SDK (7Zip)

How config Maven to work with NTLM proxy

Como utilizar a LZMA SDK (7Zip)