This document describes the method the Kephra editor is developed with.
Its highest aim is to have at all times a usable program with the
-highest quality at all levels while still
letting programming be fun.
+highest quality at all levels while still ing programming be fun.
-I strongly dislike strict rules imposed on me and ma
de fun of people that
+I strongly dislike strict rules imposed on me and mae 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? At least I use only two letters beause this is more important.
Well, several reasons brought me here.
-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.
+1.) I always wanted a sane balance between the old bureaucratic waterfall method,
+ and the modern extreme or agile programming, which is a bit too shortsighted,
+ and accumulates additional work as the project grows.
+ It should be possible to combine sound planning, practicability and quick results.
2.) Writing tests is no silver bullet and is used for several competing purposes.
-Highest aim is the conscience the code is produced with. As result you get
+Highest aim is the conscience the code is produced with. As result you get
* a superb overall user experience
* transparent project planning and status