<commit_before># Development at hudora

Here we store Information in regard to Software Development at Hudora.

## Tools

* We use [howsmycode.com][howsmycode] for code reviews. 
  ([Introduction][howsmycodeintro]) - you should create an account there
* We use [github.com/hudora][github] for version control
  ([Introduction][githubintro])  - you should create an account there
* We use [help.hudora.biz][tender] for support
  ([Introduction][tenderintro]) - you should create an account there
* We use [hudora.lighthouseapp.com][lighthouseapp] for feature requests
  ([Introduction][lighthousintro]) - you should create an account there
* [Textmate][textmatetips] is the offical Editor at Hudora Cybernetics.

[howsmycode]: http://howsmycode.com/
[howsmycodeintro]: https://cybernetics.hudora.biz/intern/wordpress/2009/12/howsmycode-erste-schritte/
[github]: http://github.com/hudora
[githubintro]: https://cybernetics.hudora.biz/intern/wordpress/2009/12/github-it-is/
[tender]: http://help.hudora.biz/
[tenderintro]: https://cybernetics.hudora.biz/intern/wordpress/2009/12/tender-it-is/
[lighthouseapp]: http://hudora.lighthouseapp.com
[lighthousintro]: https://cybernetics.hudora.biz/intern/wordpress/2009/12/lighthouse-it-is/
[textmatetips]: http://al3x.net/2008/12/03/how-i-use-textmate.html


##  Code

 * [Refactor Mercilessly][refactor] - your own code and others.
 * If you touch a file you are responsible that it is in decent shape afterwards. Even if it was messy 
   *before* you touched it.
 * Before ending the day, always check in.
 * Work in branches. For every feature/ticket create a branch. If the feature is taking more than a day
   to implement, create a fork. See [Ultimate Quality Development System][divmod] for an example how to work
   that way.
 * Check the [timeline/dashboard][timeline] regulary to see what's happening.
   Skimm the changesets and ask if you don't understand something.
 * always do `make test`, `make check` or equivalent before commit.

[refactor]: http://www.extremeprogramming.org/rules/refactor.html
[divmod]: http://divmod.org/trac/wiki/UltimateQualityDevelopmentSystem
[timeline]: https://github.com/


## Style

 * Follow [PEP 8][pep8].
   Use [pep8.py][pep8py] `--ignore=E501,W291 --repeat` to verify compliance.
 * Follow [PEP 257][pep257] for docstrings
 * No tabs. Not anywhere. Always indent with 4 spaces.
 * Wrap at Column 109
 * Use [pylint][pylint]. aim for a score of at least 8. The higher the better. If you score is below 8<commit_msg>note about wraping at line 110<commit_after># Development at hudora

Here we store Information in regard to Software Development at Hudora.

## Tools

* We use [howsmycode.com][howsmycode] for code reviews. 
  ([Introduction][howsmycodeintro]) - you should create an account there
* We use [github.com/hudora][github] for version control
  ([Introduction][githubintro])  - you should create an account there
* We use [help.hudora.biz][tender] for support
  ([Introduction][tenderintro]) - you should create an account there
* We use [hudora.lighthouseapp.com][lighthouseapp] for feature requests
  ([Introduction][lighthousintro]) - you should create an account there
* [Textmate][textmatetips] is the offical Editor at Hudora Cybernetics.

[howsmycode]: http://howsmycode.com/
[howsmycodeintro]: https://cybernetics.hudora.biz/intern/wordpress/2009/12/howsmycode-erste-schritte/
[github]: http://github.com/hudora
[githubintro]: https://cybernetics.hudora.biz/intern/wordpress/2009/12/github-it-is/
[tender]: http://help.hudora.biz/
[tenderintro]: https://cybernetics.hudora.biz/intern/wordpress/2009/12/tender-it-is/
[lighthouseapp]: http://hudora.lighthouseapp.com
[lighthousintro]: https://cybernetics.hudora.biz/intern/wordpress/2009/12/lighthouse-it-is/
[textmatetips]: http://al3x.net/2008/12/03/how-i-use-textmate.html


##  Code

 * [Refactor Mercilessly][refactor] - your own code and others.
 * If you touch a file you are responsible that it is in decent shape afterwards. Even if it was messy 
   *before* you touched it.
 * Before ending the day, always check in.
 * Work in branches. For every feature/ticket create a branch. If the feature is taking more than a day
   to implement, create a fork. See [Ultimate Quality Development System][divmod] for an example how to work
   that way.
 * Check the [timeline/dashboard][timeline] regulary to see what's happening.
   Skimm the changesets and ask if you don't understand something.
 * always do `make test`, `make check` or equivalent before commit.

[refactor]: http://www.extremeprogramming.org/rules/refactor.html
[divmod]: http://divmod.org/trac/wiki/UltimateQualityDevelopmentSystem
[timeline]: https://github.com/


## Style

 * Wrap code at line 110. If you use Textmate type
   `defaults write com.macromates.textmate OakWrapColumns '( 40, 72, 78, 109 )'` to make wraping
   more comfortable.
 * Follow [PEP 8][pep8].
   Use [pep8.py][pep8py] `--ignore=E501,W291 --repeat` to verify compliance.
 * Follow [PEP 257][pep257] for docstrings
 * No tabs. Not anywhere. Always indent with 4 spaces.
 * Wrap at Column 109
 * Use [pylint][pylint]. aim for a score of at least 8. The higher the better. If you score is below 8
{'fraction_non_alphanumeric': 0.116198537899192, 'fraction_numerical': 0.024047710657945365, 'mean_word_length': 4.432601880877743, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 10, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 8, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7184883', 'n_tokens_mistral': 1810, 'n_tokens_neox': 1638, 'n_words': 529}