Extreme Optimization >
Resources >
Current Page >
Principles of Extreme Optimization
Extreme Optimization Resources
As the name suggests, Extreme Optimization shares some principle
with Extreme Programming (XP).
-
Test-based. In XP, a collection of tests determines whether the
program is accurate. The same applies in extreme optimization. The test suite
determines whether the solution is acceptable.
-
Simplicity. The simplest, most elegant solution is very often
also close to an optimal one. Your optimized solution should not be
significantly more complex than the original.
-
Incremental Change. Always start with a solution that works.
Make a series of small changes towards your fully optimized solution. Test your
solution after every change to make sure it is still correct. Making lots
of changes all at once is not recommended.
-
Quality. There is no room for compromise here. Your client
expects excellence and that is what should be delivered.
In addition, eXxtreme Optimization adds a few principles of its own:
-
Optimize everything. That includes you, the developer! Only
optimize when necessary. Don't waste your time on ineffective improvements, or
on optimizations that the compilers will do for you.
-
Think out of the box. The most obvious solution may not be the
optimal one. Let your mind wander and see if it comes up with any alternative
representations or metaphors for your problem.
Copyright 2004-2008,
Extreme Optimization. All rights reserved.
Extreme Optimization, Complexity made simple, M#, and M
Sharp are trademarks of ExoAnalytics Inc.
Microsoft, Visual C#, Visual Basic, Visual Studio, Visual
Studio.NET, and the Visual Studio Logo are registered trademarks of Microsoft Corporation