Clean Code: Eternal Practices – Jakub Pilimon

Discover the eternal practices of clean code, where maintainability and understandability are key. Learn how to apply principles like separation of concerns, modularity, and cognitive load reduction to write code that's easy to read and maintain.

Key takeaways

Clean code is not about writing perfect code, but about making it maintainable and understandable for others.
Code duplication is not always bad, as it can evolve differently and make it easier to understand.
Code should be modular, with each module having its own responsibility and not mixing different concerns.
The Don't Repeat Yourself principle should be applied, not just in code, but in how we think about problems.
Behavioral strategies can be used to encapsulate different behaviors and make code more maintainable.
Cognitive load should be reduced by separating concerns and making code more modular.
The as if question can be used to identify the underlying principles and rules that govern a system.
The game of chess can be used as an example to illustrate how to simplify complex concepts and make them more understandable.
Bounded contexts can be used to identify the different domains and languages that exist in a system.
The Stability concept can be applied to code, making it more maintainable and understandable.
The Observable Behavior concept can be used to identify the essential behavior of a system and make it more testable.
The Model can be used to encapsulate the behavior and state of a system, making it more maintainable and understandable.
The Cohesion concept can be used to identify whether code is logically related and can be separated into different modules.
The Separation of Concerns concept can be used to identify whether code is separate into different modules that have their own responsibilities.
The Testability concept can be used to identify whether code can be tested independently and make it more maintainable.

Clean Code: Eternal Practices – Jakub Pilimon

More talks