about one thing. Meetings get more productive too when arguing has a common basis.
User docs, developer docs and comments, as well as the code itslef are means of
-communication between people. They have to
therefore cooperate seamlessly.
+communication between people. They have to cooperate seamlessly.
All these parts should have a common language and define key words and phrases
-in the exactly same way. Less friction here is an enormous productivity boost.
-A further reason, why they gotta be written altogether and by the same people.
+in the exactly same way. Less friction here is an enormous productivity boost -
+a further reason, why they gotta be written altogether and by the same people.
+Things not always turn out as planned. So quite often the docs have to be adjusted
+after the implementation of a feature. That oughta be done anyway, because the
+first phase docs were just sketchy drafts, stating what you could know then,
+which always becomes more after the coding. Small iterations between these states
+amplify an holistic understanding and overall quality. The exact rules how to
+iterate are part of the chapter L<Itersations>.
see more in L<lib/Kephra/Versioning.pod>