What is Clean Code?

Code is clean if it can be understood easily – by everyone on the team. With understandability comes readability, changeability, extensibility and maintainability.  Clean code can be read and enhanced by a developer other than its original author. Please note "working code" is not the same as "clean code"!  

"Clean Code" by Robert C. Martin is a highly regarded book in the software development community, offering valuable insights and principles for writing maintainable, readable, and efficient code. 

If reading is not your cup of tea, below Udemy courses can be followed: 

1) Learn to Write Clean Code with Java : 

Learn to Write Clean Code with Java. You can get Hands-on with Code Examples involving 4 principles of Simple Design, Refactoring & TDD.

2) Clean Code : 

This course is a compilation of common patterns, best practices, principles and rules related to writing clean code. Basic programming knowledge (no matter which language) is required!

Clean code follows a set of principles that promote simplicity, clarity, and consistency in its structure and design.. Here are some key recommendations from the book:

Meaningful Names: Use descriptive and meaningful names for variables, functions, classes, and other elements of your code. Names should convey the purpose and intent of the entity they represent.

Functions: Keep functions small, focused, and with a single responsibility. Aim for functions to be no longer than a few lines and to have a clear purpose. Use descriptive names for functions that reflect what they do.

Comments: Write clear and concise comments to explain complex algorithms, design decisions, or any code that might be unclear to others. However, strive to write self-explanatory code that doesn't rely heavily on comments to be understood.

Formatting: Follow consistent formatting conventions throughout your codebase. Use proper indentation, spacing, and line breaks to enhance readability. Consider using automated code formatting tools to enforce consistency.

Error Handling: Handle errors gracefully and provide meaningful error messages to aid debugging and troubleshooting. Use exceptions for exceptional situations and avoid using error codes or magic values for error handling.

Testing: Write automated tests to verify the correctness and behavior of your code. Aim for high test coverage and use techniques such as unit testing, integration testing, and mocking to ensure comprehensive test coverage.

SOLID Principles: Understand and apply the SOLID principles (Single Responsibility Principle, Open/Closed Principle, Liskov Substitution Principle, Interface Segregation Principle, Dependency Inversion Principle) to design modular, maintainable, and flexible software components.

Refactoring: Continuously refactor your code to improve its design, readability, and maintainability. Refactoring should be a regular part of the development process and should be supported by automated tests to ensure that existing functionality isn't broken.

Code Reviews: Encourage code reviews as a collaborative practice to catch potential issues, share knowledge, and ensure adherence to coding standards and best practices.

Continuous Learning: Stay curious and continuously seek to improve your skills and understanding of software development principles, techniques, and technologies.

In the ever-evolving landscape of software engineering, writing clean and maintainable code is crucial not only for the success of a project but also for the sanity of developers involved. Make sure your keep the sanity of everyone intact :)