Clean Code Principles Slide

12. Schedule Time to Lower Technical Debt 11. Favor High Cohesion 10. Favor Loose Coupling 9. Program with Intention 8. Avoid Primitive Obsession 7. Prefer Clear Code over Clever Code 6. Apply Zinsser’s Principle on Writing 5. Comment Why, not What 4. Avoid Long Methods—Apply SLAP 3. Give Good Meaningful Names 2. Do Tactical Code Reviews 1. Reduce State & State Mutation

A speaker presents a numbered slide listing principles for writing clean, maintainable software, while an audience watches in a dark conference room. The joke is the overly serious, exhaustive list of programming advice, making it useful as a reaction to discussions about code quality, technical debt, or developer best practices.

• @ithueti / 1209 2019-08-24