Clean coding resources

Concepts

Clean code

Clean code is a term coined by Robert C. Martin in his book Clean Code: A Handbook of Agile Software Craftsmanship. Clean code aims to be understandable by everyone that needs to work on the code.

DCI

Data, Context and Interactions are seen as a complement to MVC. It's invented by Trygve Reenskaug, who also invented MVC itself. It seperates the domain model (data) from use cases (context) and Roles that objects play (interaction). It allows you to seperate the business logic (your application), from the delivery (the framework).

Categorization creep

The urge (mainly in developers) to categorize everything. Epsecially when naming classes, developers tend to familiar categories. In practice, you can just have classes that aren't Services, Usecases, Interactors or any other special name.

Articles

• The Clean Architecture
• Well designed application architectures - Part 1
• Well designed application architectures - Part 2
• Well designed application architectures - Part 3
• The repository pattern

Presentations

• Trygve Reenskaug - DCI: Re-thinking the foundations of object orientation and of programming
• Robert C. Martin - Keynote: Architecture the Lost Years
• Jim Coplien - DCI: Practical Tips and Lessons for Nerds
• Jim Coplien - Why DCI is the Right Architecture for Right Now

Example projects

• Starling (Ruby)
• Example Kohana Business Logic (PHP)
• Example browser game showing decoupling of delivery and storage (PHP)
• Example application showing Entity-Boundary-Interactor (PHP)