Software Laws

Change: certanity in the future

Defect: if change the code

Simplicity:  individual piece as simple

Testing: show how behaves as you tested.

Software Fact

• Maintaince is more important than implementation
• The effort of maintaince proportional with complexity

Fact

• understand the domain
• help to people
• if complex is overenginerring

Rule

• Simple to other programmers
• decisions by indivuals (no democracy)
• don’t predict the future
• don’t write until need
• BEST design allowed
• most change in environment
• least change in the software
• Difficult design solve on paper
• Complexity grows
• expanding purpose
• adding other programmers
• changing if don’t need
• locked into bad technologies
• misunderstanding
• ERROR in design
• reinventing the wheel
• Complexity reduce
• redesign in small piece of the code in steps
• wrapped the complex code