Can I find the code related to the problem or the requested change? Go +od Naming, High Cohesion, Single Responsibility Principle, Separation + of Concerns Can I understand the code? Good Naming, Composed Method, The Principle + of Least Surprise, Can You See The Flow of the Code?, Encapsulation Is it easy to change the code? Don't Repeat Yourself, Wormhole Anti-Pa +ttern, Open Closed Principle Can I quickly verify my changes in isolation? Loose Coupling, High Coh +esion, Testability Can I make the change with a low risk of breaking existing features? L +oose Coupling, High Cohesion, Open Closed Principle, Testability Will I know if and why something is broken? Fail Fast
In reply to Re: Code Maintainability
by ady
in thread Code Maintainability
by mpeever
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |