Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re: Code Maintainability

by ady (Deacon)
on Dec 05, 2008 at 06:44 UTC ( #728199=note: print w/ replies, xml ) Need Help??


in reply to Code Maintainability

Interesting discussion, but apart from (and above, really) the syntax (incl. comments) impact on semantics, I find that code design is of superior importance for maintainability; Consider design principles such as Separation of Concerns, Orthogonality, Extensibility, Testability (quote On-Writing-Maintainable-Code) :

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

Best regards,
Allan Dystrup


Comment on Re: Code Maintainability
Download Code

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://728199]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (5)
As of 2015-07-28 01:36 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (251 votes), past polls