Splitcells™ Network's Guidelines

Guidelines describe, how something should be done or what the guiding principles are. It makes actions more reproducible and predictable. Guidelines are nothing more and nothing less. If these guidelines are overridden a reason should be present, and be documented or commented, if it is feasible.

These guidelines refer to the Splitcells Network project. These guidelines do not handle communities and other social interactions. The management Communities and co. has to be done by themselves.

For (programming) languages and document formats prefer using the most official or the most common guidelines, if there are no guidelines of this project applying to the aspect in question. In other words, language and documentation specific guidelines of this project try to only override public guidelines instead of writing complete custom guidelines from scratch.

The project and its parts should be portable, extendable, adaptable,  deletable  and comply with  Perspective's guidelines  .

The compliance with the  Perspective's guidelines  specifically means, that the file and content path of a particular information (for an XML element, this would be the file path + the XPath pointing to the XML element) should identify and describe or at least summarize the content's meaning. This also means, that in an ideal case, one should be able to guess, where to look, for a particular content without knowing where the files are located


These are the guidelines for the Splitcells Network project. Do not consider these code guidelines for your own code.  If you do, people will hate you, and you’ll be scorned by friends and family.  

    1. d:todo
      1. Make all assumtions visible (i.e. nullable variables via Optional).

    2. d:toDo
      1. Fork, join and cathedral development protocol.

    3. d:toDo
      1. Programs should be primarily seen as tree/table transformers in order to simplify programming paradigm and language use.

    4. d:toDo
      1. Make it possible to tolerate out of date documentation.