<commit_before>Up to Date
=
Will help keep your maven project dependencies up to date

This is a work in progress.  This readme will be updated when it is in a functional state.

Currently you will not be able to compile the console module without setting up [dependency analyzer](https://github.com/SeanShubin/dependency-analyzer) and [dot](http://graphviz.org) first.

If dependency analysis is not important to you, you can just disable the exec-maven-plugin entry in the console module

Design by Contract Presentation
=
- Maintainable Code
- Easy to Test
- Design By Contract
    - Object-Oriented Software Construction - Bertrand Meyer
        - Pre-conditions
        - Post-conditions
        - Invariants
    - Contract of a function
        - input -> function -> output
    - Contract of constructor injection
        - collaborators -> constructor -> instance
- Should x be behind a contract?
    - Sometimes this is a judgment call, sometimes there is a correct answer
    - If the code is more comprehensible as a unit, it should not be split into contracts<commit_msg>Updated presentation<commit_after>Up to Date
=
Will help keep your maven project dependencies up to date

This is a work in progress.  This readme will be updated when it is in a functional state.

Currently you will not be able to compile the console module without setting up [dependency analyzer](https://github.com/SeanShubin/dependency-analyzer) and [dot](http://graphviz.org) first.

If dependency analysis is not important to you, you can just disable the exec-maven-plugin entry in the console module

Design by Contract Presentation
=
- Maintainable Code
- Easy to Change
- Easy to Test
- Design By Contract
    - Object-Oriented Software Construction - Bertrand Meyer
        - Pre-conditions
        - Post-conditions
        - Invariants
    - Contract of a function
        - input -> function -> output
    - Contract of constructor injection
        - collaborators -> constructor -> instance
    - Expressiveness of contract
        - Static Typing
        - Protocols        
- Should x be behind a contract?
    - Sometimes this is a judgment call, sometimes there is a correct answer
    - If the code is more comprehensible as a unit, it should not be split into contracts
{'fraction_non_alphanumeric': 0.053626373626373625, 'fraction_numerical': 0.0, 'mean_word_length': 3.0426287744227354, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 11, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6970002', 'n_tokens_mistral': 563, 'n_tokens_neox': 543, 'n_words': 283}