<commit_before>:numbered!:

[[bibliography]]
[appendix]
== Bibliography

* [[[AntiPatterns]]] <NAME>: AntiPatterns: Refactoring Software,
 Architecture and Projects in Crisis, <NAME> & Sons, 1998 -- a tried and
 true work on things that tend to go wrong in software development and other
 projects.

* [[[arc42]]] arc42 - Resources for Software Architects. Practical template, liberal licence.
Available in a variety of formats, see http://arc42.de[German website] or http://arc42.org[English website].

* [[[Agans-Debugging]]] <NAME>: Debugging: The 9 Indispensable Rules for Finding Even the Mose
Elusive Software and Hardware Problems. Amacom Press, 2002. Although most developers take "debugging skills" for granted,
they sometimes spend too much time tracking too little bugs.

* [[[AIW]]] http://www.sei.cmu.edu/architecture/tools/evaluate/aiw.cfm[Architecture Improvement Workshop].
Software Engineering Institute, Carnegie Mellon University.

* [[[Annett-Legacy]]] <NAME>: Working with Legacy Systems: A practical guide to the real systems we inherit.  http://leanpub.com/WorkingWithLegacySystems[Leanpub Publishing].

* [[[SEI-ATAM]]] http://www.sei.cmu.edu/architecture/tools/evaluate/atam.cfm[Architecture Tradeoff Analysis Method].
Software Engineering Institute, Carnegie Mellon University.


* [[[Berglung-AfferentCoupling]]] <NAME> (GitHub) on
http://de.slideshare.net/jaxlondon2012/complexity-theory-and-software-development-tim-berglund[Complexity Theory and Software Development]. Look at slide 73ff on afferent coupling - and keep that in mind for your own refactorings.

* [[[Bass09]]] <NAME> et.al.: Software Architecture in Practice. Addison-Wesley, 2. Edition 2009.

//* [[[Big-Ball-Of-Mud]]] <NAME> and <NAME>, http://laputan.org/mud/[Big Ball of Mud] - very influentual paper from the http://st-www.cs.uiuc.edu/~hanmer/PLoP-97/[fourth conference on Patterns languages of Program Design, PLoP97]
* [[[Big-Ball-Of-Mud]]] <NAME> and <NAME>, http://laputan.org/mud/[Big Ball of Mud] - very influentual paper from the http://hillside.net/plop/plop97/[fourth conference on Patterns languages of Program Design, PLoP97]


* [[[Bommer-Wartung]]] <NAME>, <NAME>, <NAME>: Softwarewartung: Grundlagen, Management und Wartungstechniken.
(in German) dpunkt Verlag, 2008. Interesting treatment of categories of software systems and their respective need for maintenance and evolution. Authors quote studies from Lehman and Belady from the 1970's.

* [[[Boy-Scout-Rule-article]]] The Boy Scout Rule, see http://programmer.97things.oreilly.com/wiki/index.php/The_Boy_Scout_Rule

* [[[Brodie-Stonebraker]]] Brodie, M. and Stonebraker, M: Migrating Legacy Systems: Gateway, Interfaces & the Incremental Approach; Morgan Kaufmann 1995.

* [[[Clements-ATAM]]] <NAME> et.al.: Evaluating Software Architecture - Methods and Case Studies.
Addison-Wesley, 2001. Detailed overview of ATAM (and other evaluation methods).


* [[[Campbell14]]] Ann Campbell et. al: SonarQube in Action. Manning Publications, 2014. Great introduction to
the flexible, multi-language code-analysis toolkit.<commit_msg>some microscopical changes in Bibliography<commit_after>:numbered!:

[[bibliography]]
[appendix]
== Bibliography

* [[[AntiPatterns]]] <NAME>: AntiPatterns: Refactoring Software,
 Architecture and Projects in Crisis, <NAME> & Sons, 1998 -- a tried and
 true work on things that tend to go wrong in software development and other
 projects.

* [[[arc42]]] arc42 - Resources for Software Architects. Practical template, liberal licence.
Available in a variety of formats, see http://arc42.de[German website] or http://arc42.org[English website].

* [[[Agans-Debugging]]] <NAME>: Debugging: The 9 Indispensable Rules for Finding Even the Mose
Elusive Software and Hardware Problems. Amacom Press, 2002. Although most developers take "debugging skills" for granted,
they sometimes spend too much time tracking too little bugs.

* [[[AIW]]] http://www.sei.cmu.edu/architecture/tools/evaluate/aiw.cfm[Architecture Improvement Workshop].
Software Engineering Institute, Carnegie Mellon University.

* [[[Annett-Legacy]]] <NAME>: Working with Legacy Systems: A practical guide to the real systems we inherit.  http://leanpub.com/WorkingWithLegacySystems[Leanpub Publishing].

* [[[SEI-ATAM]]] http://www.sei.cmu.edu/architecture/tools/evaluate/atam.cfm[Architecture Tradeoff Analysis Method].
Software Engineering Institute, Carnegie Mellon University.


* [[[Berglung-AfferentCoupling]]] <NAME> (GitHub) on
http://de.slideshare.net/jaxlondon2012/complexity-theory-and-software-development-tim-berglund[Complexity Theory and Software Development]. Look at slide 73ff on afferent coupling - and keep that in mind for your own refactorings.

* [[[Bass09]]] <NAME> et.al.: Software Architecture in Practice. Addison-Wesley, 2. Edition 2009.

* [[[Big-Ball-Of-Mud]]] <NAME> and <NAME>, http://laputan.org/mud/[Big Ball of Mud] - very influentual paper from the http://hillside.net/plop/plop97/[fourth conference on Patterns languages of Program Design, PLoP97]


* [[[Bommer-Wartung]]] <NAME>, <NAME>, <NAME>: Softwarewartung: Grundlagen, Management und Wartungstechniken.
(in German) dpunkt Verlag, 2008. Interesting treatment of categories of software systems and their respective need for maintenance and evolution. Authors quote studies from Lehman and Belady from the 1970's.

* [[[Boy-Scout-Rule-article]]] The Boy Scout Rule, see http://programmer.97things.oreilly.com/wiki/index.php/The_Boy_Scout_Rule

* [[[Brodie-Stonebraker]]] <NAME>. and <NAME>: Migrating Legacy Systems: Gateway, Interfaces & the Incremental Approach; <NAME> 1995.

* [[[Clements-ATAM]]] <NAME>s et.al.: Evaluating Software Architecture - Methods and Case Studies.
Addison-Wesley, 2001. Detailed overview of ATAM (and other evaluation methods).


* [[[Campbell14]]] Ann Campbell et. al: SonarQube in Action. Manning Publications, 2014. Great introduction to
the flexible, multi-language code-analysis toolkit.
{'fraction_non_alphanumeric': 0.11767659859390693, 'fraction_numerical': 0.020087043856712422, 'mean_word_length': 5.230448383733055, 'pattern_counts': {'":': 0, '<': 32, '<?xml version=': 0, '>': 32, 'https://': 0, 'lorem ipsum': 0, 'www.': 5, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4874835', 'n_tokens_mistral': 1974, 'n_tokens_neox': 1744, 'n_words': 608}