Principles for writing clean code and being effective in doing so. Let's look at these four uncles Bob's teachings.

I've learned a lot about the guidelines for producing clean code from listening to Uncle Bob, one of the best software engineers out there. These are the four tried-and-true principles that I personally preach..

1. No one writes clean code first, they figure it out and clean it up?

This is a common approach in software development in which a program is initially written to meet the requirements and then refactored and optimized to improve readability, maintainability, and performance. While writing clean code from the start is an ideal goal, it may take several iterations to achieve that level of quality. The key is to constantly strive to improve and clean up the code with each iteration.

2. The slower the code, the cleaner

?It is not always true that slower code is cleaner. Clean code is frequently defined as code that is simple to read, maintain, and comprehend while remaining efficient. Writing clean code versus writing fast code can be a trade-off because sometimes we push before realizing some stuff. Code should ideally be both clean and fast, but sometimes compromises must be made to achieve one or the other. This does not mean you should exceed the deadline. In this case, start early.

3. Once it works, you have to spend the same amount to clean it up?

This statement is often true in software development. Clean, well-written code is easier to maintain, enhance, and debug than code that is poorly structured or contains unnecessary complexity. Cleaning up code can involve a number of tasks such as refactoring, optimizing, and documenting, and these tasks can take just as much time and effort as writing the initial code. This is why it is important to practice good software engineering principles and to prioritize code quality from the beginning of a project.

4. Care about the reader

Some Legacy codes are shitty because the developer only thinks about themselves writing them. The importance of writing code that is readable and easily understandable to others, as it can improve collaboration and maintenance of the code. Good code readability can be achieved through the use of meaningful names, consistent indentation, and clear comments that explain the purpose of the code.