highest quality at all levels while still letting programming be fun.
I strongly dislike strict rules imposed on me and made fun of people that
produce theories with three letter acronyms that try to be the answer to everything.
But now I am standing here, trying to "sell" you yet another programming methodology.
-That IS irony, isn't it?
+That IS irony, isn't it?
Well, several reasons brought me here.
-1.) All methodologies I know of overlook several aspects of the product.
+1.) I always wanted a sane balance between the old bureaucratic waterfall method
+ and a bit too shortsighted, modern extreme or agile programming, combining
+ sound planning and practicability.
+2.) Writing tests is no silver bullet and is used for several competing purposes.
+3.) The awesome powers of prototypes are still not fully used.
+4.) All methodologies I know of overlook several aspects of the product.
That includes even "documentation driven development",
which gave important impulses for the creation of CP.
-2.) I always wanted a sane balance between the old bureaucratic waterfall method
- and a bit too shortsighted, modern extreme or agile programming, combining
- sound planning and practicability.
+5.) New tools like hg or git allow new workflows which solve pending problems.
-Highest aim is the conscience the code is produced with. A superb overall
-user experience as well as good code quality should be result of it.
+Highest aim is the conscience the code is produced with. As result you get
+ * a superb overall user experience
+ * transparent project planning and status
+ * room for experiments and changes without trouble
=head2 Phases of Development
Even if productive software is never done and you wand to get something usefull