Commits

Herbert Breunung  committed 0b78150

reformulating goals of cp

  • Participants
  • Parent commits 1da9cee
  • Branches sp3

Comments (0)

Files changed (2)

File doc/CompleteProgramming.pod

 highest quality at all levels while still letting programming be fun.
 
 
+
 =head2 Overview
 
 =head3 DISCLAIMER
 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? At least I use only two letters beause this is more important.
 
-=head2 Rational
+
+=head3 Rational
 
 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.
 
-=head2 Main Goal
+=head3 Main Goal
 
-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
+   * quality code
+   * 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
 
 
+=head2 Details
+
 =head3 Defining Task
 
 main task

File lib/Kephra/Versioning.pod

 
 =over 2
 
-=item * simple (as linear as possible - as a watch)
+=item * simple (linear as a watch)
 
 =item * measures development status not time
 
 If one number is raised, all to the left get a reset to zero.
 Trailing zeros can be omited - 0.5 is the same as 0.5.0.0
 
+Some similar idea is known as semantic versioning L<http://semver.org>.
+
 =head3 Development
 
 Development number is changed after every important commit.
 =head2 What Changed?
 
 We dropped the special patchlevel number.
-The version 0.3 Patchlevel 5 is now 0.3.0.5.
+The version 0.3 Patchlevel 5 is now 0.3.0.5.