clean-code

You can refactor code to be more maintainable by applying pragmatic coding standards like SRP, DRY, KISS, and YAGNI. This ensures functions do one thing, removes duplicated logic, and reduces deep nesting to minimize defects and onboarding effort.

Best practices for reducing code duplication and complexity include applying the DRY principle to promote reuse and KISS to prefer simple solutions. Additionally, following YAGNI avoids unnecessary features, keeping the codebase concise and maintainable.

You use guard clauses to flatten deeply nested functions by checking for edge cases early and returning immediately. This promotes a flat structure, limits function length, and eliminates the need for complex conditional nesting in your modules.

You should remove comments during a code review when they are unnecessary and the code is self-documenting through clear naming conventions. Avoiding over-commenting is an anti-pattern awareness practice that keeps the logic concise and readable.

Yes, you can enforce the Single Responsibility Principle on existing modules through controlled refactoring. By breaking down God functions into smaller, dedicated components, you ensure each module does exactly one thing, improving overall maintainability.

The best way to apply coding standards to plain language prompts is to explicitly request refactoring actions, such as making functions smaller, renaming variables for clarity, and removing duplicated logic to generate concise, AI-powered code.