Bibliography

Clean Code Developer Books

• Clean Code: A Handbook of Agile Software Craftsmanship (Robert C. Martin)
• Clean Code - Refactoring, patterns, testing and techniques for clean code: German edition
• The Clean Coder: A Code of Conduct for Professional Programmers (Robert C. Martin)
• Clean Coder: Rules of conduct for professional programmers (mitp Professional)
• Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin)
• Clean Architecture - Good Software Architectures: The Practical Handbook for Professional Software Design (Robert C. Martin)
• The Pragmatic Programmer. From Journeyman to Master
• Head First Design Patterns
• Refactoring: Improving the Design of Existing Code
• Code Complete: A Practical Handbook of Software Construction: A Practical Handbook of Software Costruction
• Working Effectively with Legacy Code
• Working effectively with legacy code. Refactoring and testing existing software
• Java by Comparison: Become a Java Craftsman in 70 Examples
• The Art of Readable Code
• With Flow Design to Clean Code (Stefan Lieser)

Online articles worth reading

• Clean Code Cheat Sheet, Urs Enzler
• Clean code - from teaching to everyday lifepresentation by Jörn Vollmer and Reik Oberrath
• Ask 'Why' Five Times About Every Matter to the practice of Root Cause Analysis
• http://www.heise.de/developer/artikel/Herausforderung-Brownfield-Teil-4-Komplexitaet-bewaeltigen-durch-Differenzierung-1031414.html, 4th part of the heise Developer series about CCD
• http://www.heise.de/developer/artikel/Herausforderung-Brownfield-Teil-3-Das-Sicherheitsnetz-erweitern-956969.html, 3rd part of the heise Developer series about CCD
• http://www.heise.de/developer/artikel/Herausforderung-Brownfield-Teil-2-Das-Sicherheitsnetz-aufspannen-888901.html, 2nd part of the heise Developer series about CCD
• http://www.heise.de/developer/artikel/Clean-Code-Developer-in-Brownfield-Projekten-855114.html, 1st part of a series on CCD in brownfield projects at heise Developer
• 31 Days of Refactoring, LosTechies.com
• Technical Debt Quadrant, Martin Fowler: The four ways into technical debt
• A classic: Code as DesignJack W. Reeves
• Partial classes help the single level of abstraction principle, Ralf Westphal
• Relearning: The Productivity Problem that We're Not Supposed To Talk AboutScott Bellware takes up the cudgels for readable code
• Is Code Complete?, Saurabh_Saxena
• Law of DemeterBrad Appleton
• Paying Down Your Technical DebtJeff Atwood: What happens when projects don't take the CCD value system into account? They accumulate "technical debt". In his article, Jeff Atwood summarizes and comments on fundamental articles on the term.
• The Joel Test: 12 Steps to Better CodeJoel Spolsky: Some of his steps relate to CCD building blocks
• Source Control HOWTO, Eric Sink
• The principles of object-oriented design in http://www.galileocomputing.de/966?GPP=oppy "Object Orientation Practice Book" by Bernhard Lahres, Gregor Rayman, Galileo 2006
• SOLID Development Principles - In Motivational Picturesblog
• Domain Driven Design Quickly, eBook
• Pablo's Topic of the Month - March: SOLID Principles, Links to SOLID articles
• Real Swiss don't need SRP, do they?, Gabriel Schenker
• Open Closed Principle, Jeremy Miller, MSDN Magazine
• Cohesion and Coupling, Jeremy Miller, MSDN Magazine
• Software Creation Mystery, Andriy Solovey, Blog

Podcasts worth listening to

• .NET Rocks !#388, Bob Martin (Uncle Bob) on Being a Professional!
• .NET Rocks !#410, Uncle Bob at Oredev
• Hanselminutes Podcast 145, SOLID Principles with Uncle Bob - Robert C. Martin
• Elegant Code Cast 15, Uncle Bob Martin
• Pragmatic Programmers, Andy Hunt on pragmatic wetware Careful, link to an MP3!

Videos worth seeing

• Trends in Agile Development, Kent Beck
• Principle of Agile Design, Robert C. Martin
• Strategic Design, Eric Evans
• Putting the Model to Work, Eric Evans
• Eric Evans on DDD