How to build quality appllications: learn from UNIX | Division by Zero

Architecture, security and coding

How to build quality appllications: learn from UNIX

How to build quality appllications: learn from UNIX

Written by Division by Zero

Thursday, 01 April 2010 12:30

Every developer or architect want to develop quality systems that are highly maintainable. No matter the environment you're working with, .Net, Java or any other system, it's a good thing to keep the rules for UNIX application development. Here are the rules, keep them in mind when you're designing a system:

Rule of Modularity: Write simple parts connected by clean interfaces.
Rule of Clarity: Clarity is better than cleverness.
Rule of Composition: Design programs to be connected to other programs.
Rule of Separation: Separate policy from mechanism; separate interfaces from engines.
Rule of Simplicity: Design for simplicity; add complexity only where you must.
Rule of Parsimony: Write a big program only when it is clear by demonstration that nothing else will do.
Rule of Transparency: Design for visibility to make inspection and debugging easier.
Rule of Robustness: Robustness is the child of transparency and simplicity.
Rule of Representation: Fold knowledge into data so program logic can be stupid and robust.
Rule of Least Surprise: In interface design, always do the least surprising thing.
Rule of Silence: When a program has nothing surprising to say, it should say nothing.
Rule of Repair: When you must fail, fail noisily and as soon as possible.
Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.
Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.
Rule of Optimization: Prototype before polishing. Get it working before you optimize it.
Rule of Diversity: Distrust all claims for “one true way”.
Rule of Extensibility: Design for the future, because it will be here sooner than you think.

Make sure you understand the implications of these rules (see this link). Keep in mind that these rules have proven to work. This way it is possible to create extensible, testable, maintainable, robust and functional systems.

Tags:

Related Articles

Add comment

Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald E. Knuth

© 2009 - 2012, Division by Zero

Template based on the empire template by joomlashack

This work by Division by Zero is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Netherlands License.