Hellooooo!

Summary of this email:

• 4 design rules to make your code simpler (+ course on the topic).
• New ManagerPro course on Conflict Management: Common Mistakes

Estimated reading time: 3 minutes.

🗒️ 4 design rules to make your code simpler

In the world of programming, there are 4 design rules to make our code simpler. Following them makes our code more maintainable, especially in the long run.

But, like all rules, you also need to know when to break them. The rules, defined by Kent Beck, are:

1️⃣ Reveals intention Code should clearly explain what it does and why, without needing to read comments or having to ask the person who wrote it (that person might be you from a few months ago).

Variable, function, and class names should be expressive. The logic flow should be easy to follow.

2️⃣ Minimize the number of elements The fewer concepts, classes, functions, and modules there are, the easier it is to understand and maintain the system.

There's a point where if you try to minimize too much, the code can become too coupled, so be careful not to overdo it.

3️⃣ No duplication If the same knowledge or logic exists in more than one place, someone in the future will have to change it in all of them.

There are various techniques for handling this, but the most recommended is the Rule of 3: Don't consider abstracting it until you've seen it duplicated 3 times.

4️⃣ Passes the tests Code must fulfill its purpose and work as expected.

- New code comes with tests. - Refactored code doesn't break tests. - If there's a bug, it gets tested and reproduced.

With these 4 simple rules, you can achieve simpler, more elegant, and longer-lasting code.

If you want to learn when and how to apply these rules, we've just published a course on it for Codely Pro Premium: 4 Rules of Simple Design.

💥 New ManagerPro course on Conflict Management: Common Mistakes

Learn to recognize the most common mistakes in conflict management and discover how to avoid them with real examples and simulated scenarios.

In this course, we explore the most common failures that arise when managing conflicts. Through simulated scenarios and situations inspired by real cases, we analyze what happened, why it happened, and what alternatives were possible.

We'll also look at anti-patterns to sharpen your eye: helping you recognize patterns, nuances, and opportunities that often go unnoticed.

It's a useful course for those who already have a foundation in conflict resolution and want to see more tools and realistic examples to strengthen their judgment and skills.

You can sign up for ManagerPro here. 😊

And since you've made it this far in the newsletter, here's the joke of the week, which I know you were waiting for:

> Why do programmers prefer dark mode? Because light attracts bugs! 😂

Cheers!