#30: Weekly Recap — Code Health

Happy Friday! Here is your weekly recap of The Coder Cafe on the theme of code health.

As always, don't feel bad if you haven't had time to read all the posts this week. What's important is to keep moving forward, no matter the pace. Focus on the journey, not just the destination.

Visual of the Week

Credits

Issues

• #26: Readability

• #27: Simplifying Complex if Statements

• #28: Cohesion

• #29: Coupling

Weekly Podcast

Knowledge Check

1. What’s the definition of readability?

2. Why should we aim for readable code?

3. Can you think of at least three readability principles?

4. Have you really written readable code this week? 🙂

5. How can we simplify complex if statements?

6. What’s the definition of cohesion?

7. Why should we aim for low cohesion?¹

8. Can you think of at least two code smells showing a lack of cohesion?

9. Can you think of at least three types of cohesion?

10. What’s the definition of coupling?

11. Why should we aim for low coupling?

12. What is the relationship between cohesion and coupling?

13. Can you think of at least two types of coupling?—Bonus point if you can think about my favorite!

14. Can you think of an example in your codebase or system where coupling could be loosened?

Explore Further

• The art of readable code

• Software engineering at Google - Readability section

• Loose & tight coupling: why code is hard to change

• Coupling, cohesion & connascence

---

Next week, the theme will be… database fundamentals! 🎉

1. It was a mistake on purpose. I just wanted sure reading that low cohesion as a goal triggered something in you 😉.