th3alch3m1st/awesome-clean-code

Awesome Clean Code

Design Principles

SOLID

Acronym coined by Robert C. Martin (Uncle Bob) to descibe the following five principles:

1. The Single Responsibility Principle A class should have only one reason to change.
2. The Open Closed Principle Software entities should be open for extension, but closed for modification.
3. The Liskov Substitution Principle Derived classes must be substitutable for their base classes.
4. The Interface Segregation Principle Make fine grained interfaces that are client specific.
5. The Dependency Inversion Principle Depend on abstractions, not on concretions.

A local copy of "Design Principles and Design Patterns" by Robert C. Marin from objectmentor.com website. More about this principles with examples can be found here

Kent Beck's Four Rules of Simple Design

A design which:

1. Passes all tests.
2. Reveals intention.
3. No duplication.
4. Fewest elements.

Elegant Objects

1. No null.
2. No code in constructors.
3. No getters and setters.
4. No mutable objects.
5. No static methods, not even private ones.
6. No instanceof, type casting, or reflection.
7. No public methods without @Override.
8. No statements in test methods except assertThat.
9. No implementation inheritance.

Featured Articles

• When A Method Can Do Nothing
• Tell Don't Ask
• Converting Queries to Commands
• Object Calisthenics
• How Interfaces Are Refactoring Our Code
• Your Constructors are Completely Irrational
• Class naming
• Names objects after things, not actions!
• Interfacing with hard-to-test third-party code
• How to Think About the "new" Operator with Respect to Unit Testing
• Avoiding Repetition
• Design Principles from Design Patterns - A Conversation with Erich Gamma
• Programming Like Kent Beck
• How Immutability Helps
• Clean Architecture
• Hexagonal Architecture: three principles and an implementation example
• Getting Started With DDD When Surrounded By Legacy Systems

Tutorials

• Refactoring a JavaScript video store
• Bowling Game Kata
• Refactoring from anemic model to DDD
• Writing Testable Code
• Essential Skills for Agile Development
• First Pop Coffee Company
• Testing legacy by Sandro Mancuso, part 2, and video
• Live Refactoring Towards Solid Code
• Introducing the Gilded Rose kata and writing test cases using Approval Tests by Emily Bache, part 2 and part 3
• Domain Driven Design Crash Course
• Reactive in practice: A complete guide to event-driven systems development in Java
• Writing Clean Tests

Videos

• How To Design A Good API and Why it Matters by Joshua Bloch
• Inheritance, Polymorphism, & Testing
• Don't Look For Things!
• Don't Create Objects That End With -ER
• 8 Lines of Code by Greg Young Accompanied slides
• 19 1/2 Things to Make You a Better Object Oriented Programmer Nice summary
• Railway oriented programming: Error handling in functional languages
• Yves Reynhout - Trench Talk: Evolving a Model
• Seven Ineffective Coding Habits of Many Programmers by Kevlin Henney
• Java Optional - The Mother of All Bikesheds by Stuart Marks

Code Examples

• Code Katas
• hentai
• Source code for the book, "Growing Object-Oriented Software, Guided by Tests"
• jcabi-email
• Assignment done for some interview

Git Hub

• Nat Pryce
• Steve Freeman
• Matteo Vaccari

Blogs

• Martin Fowler
• Michael Feathers
• Robert C. Martin (Uncle Bob)
• Yegor Bugayenko
• Code Cop
• The Code Whisperer
• jbrains.ca
• Nat Pryce
• Steve Freeman
• Miško Hevery
• Matteo Vaccari
• Carlo Pescio
• Jeffrey Palermo
• Kenneth Truyers
• Vaughn Vernon
• Codurance
• Mihai
• Enterprise Craftsmanship
• The Iterate Blog
• The Holy Java

Twitter

• Kent Beck
• Martin Fowler
• Robert C. Martin
• Ron Jeffries
• Michael Feathers
• Yegor Bugayenko
• Carlo Pescio
• Matteo Vaccari
• Jeffrey Palermo
• Kenneth Truyers
• Greg Young
• Eric Evans
• Vaughn Vernon

Books

• Refactoring: Improving the Design of Existing Code by Martin Fowler errata for the book can be found here
• Clean Code by Robert C. Martin
• Design Patterns: Elements of Reusable Object-Oriented Software
• Elegant Objects by Yegor Bugayenko
• Growing Object-Oriented Software, Guided by Tests

Other

• Code Katas