Clean code starts with readability. Use meaningful variable and function names, and follow consistent naming conventions throughout your project. When someone else (or even you, a few months later) reads your code, clear names and consistent structure make understanding it much easier.

Consistent formatting also plays a crucial role. Stick to a style guide for indentation, spacing, and bracket placement. Tools like Prettier or ESLint can automate this, ensuring that every team member’s code looks uniform and professional.

Breaking your code into small, single purpose functions makes it easier to test, debug, and maintain. Each function should do one thing and do it well. This reduces the risk of unexpected side effects when changes are made and makes code reuse much simpler.

Modules and classes should follow the same principle. Instead of creating a large file with multiple responsibilities, separate your logic into well defined components. This helps new developers quickly understand the system and locate the code they need to work on.

Avoid duplicating code at all costs. Repeated code increases maintenance overhead and the chance of introducing bugs. Instead, extract common logic into reusable functions or utilities.

Finally, write code with future changes in mind. Anticipate potential growth and design your modules to be flexible and extensible. This forward thinking approach prevents messy rewrites later and keeps your codebase clean over time.