Clean code theory in English
Table of contents
Clean Code Theory
What do the colors mean ?
When do i change from one color to another ?
What does red, orange, yellow, green and blue mean ?
How can i motivate other developers ?
How could we improve the quality of this article ?
Source code convention tools
Literature, good books and references
How can i subscribe/feed this blog ?
Want to stay up to date ?
How can i rate this blog ?
Where do i find more clean code knowledge and gadgets?
Clean Code Theory
Hi there! Inspired by the geman website www.clean-code-developer.de i have lauched the treslines.com initiative with the aim to make it also popular to the english speakers. In this blog i wanna make you familiar with the basic colors of the clean code initiative and its meaning.
What do the colors mean ?
Well, In the initiative there are 7 rotational degrees. It starts from black, thru red, orange, yellow, green, blue till white. Black means only that you are interested in learn more about it and are preparing yourself to get started. Personally, i do not thing that we nescessarily need this degree. It says only that you are interested in it. www.treslines.com offers gadgets to support the iniciative. There you’ll never find the colors black and white. The white degree means that the developer are working with a huge openminded horizont. Instead of wearing the white degree, the developer should turn back to the first degree and start it from the beginning again. Thats the reason we say ratational degrees.
When do i change from one color to another ?
Well, thats up to you. I recommend a period of 1-2 month each degree.
What does red, orange, yellow, green and blue mean ?
These are interesting degrees. In it we will find always design principles to apply and best practises to use. Check www.treslines.com for gadgets and know how about clean code as well agile development.
Principles
1. Don't Repeat Yourself (DRY)
2. Keep It Simple, Stupid (KISS)
3. Favor Composition over Inheritance (FCoI)
4. Beware of Optimisations (BoO)
Practises
1. Scouts rules
2. Root Cause Analysis
3. Version Control
4. Simple Refactoring
5. Daily Reflection of your Work
Principles
1. Single Level of Abstraction (SLA)
2. Single Responsability Principle (SRP)
3. Separation of Concerns (SoC)
4. Source Code Conventions
Practises
1. Issue Tracking
2. Auto Integration Tests
3. Read, read, read
4. Reviews
Principles
1. Interface Segregation Principle (ISP)
2. Dependency Invertion Principle (DIP)
3. Liskov Substitution Principle (LSP)
4. Principle of Least Astonishment (PoLA)
5. Information Hiding Principle (IHP)
Practises
1. Auto Unit Tests
2. Mockups
3. Code Coverage Analyse
4. Participation in professional events
5. Complex Refactoring
Principles
1. Open Close Principle (OCP)
2. Tell don't ask
3. Law of Demeter (LoD)
Practises
1. Continuous Integration I
2. Static Code Analysis
3. Inversion of Control Container
4. Expirience sharing
5. Measure of ErrorsPrinciples
1. Design & Implementation do not overlap (no inconsistency)
2. Implementation reflects design
3. You Ain't Gonna Need It (YAGNI)
Practises
1. Continuous Integration II
2. Iterative development
3. Component orientation (package structure)
4. Test First
How can i motivate other developers ?
Well i do that by talking about, i wear my treslines.com t-shirt, i wear my bracelets with the CCD (Clean Code Developer Initials and colors) and i use my brand new treslines bag. It feels fantastic and even on the train people start talking to me asking about it. It is also a great idea to motivate agile teams and to share your expirience. You may want a great gift to show your appreciation to your team. Surprise them with a gadget from www.treslines.com. I love it.
