clean-code

To improve code readability during a code review, enforce meaningful naming conventions, small functions with zero to two arguments, and clean error handling to eliminate code smells and reduce confusion across the codebase.

The Single Responsibility Principle (SRP) dictates that functions should operate at a single abstraction level. Applying SRP means preferring functions of four to six lines with no side effects, ensuring code remains maintainable and focused.

Refactor a long function by applying the Boy Scout Rule and Extract Till You Drop technique. Incrementally extract small, single-level functions to address misabstraction, remove duplication, and improve overall code quality.

Error handling and unit testing should be structured by separating concerns and using exceptions. This separation promotes robust unit tests, ensuring your codebase remains reliable and maintainable without mixing business logic with error management.

Yes, this clean code approach applies directly to architecture planning across software teams. It enforces naming, function size, and testing discipline, ensuring architectural designs remain readable and maintainable at scale. For deeper structural design, consider clean-architecture.

Avoid applying clean code refactoring techniques like Extract Till You Drop when functions already operate at a single abstraction level or when incremental changes would introduce unsafe patterns and break existing unit tests.