From d108b60389dfd52cd0e996817f1213979a66de78 Mon Sep 17 00:00:00 2001
From: Mitsuo Tokumori <rtokumori@pucp.edu.pe>
Date: Tue, 19 Sep 2023 14:02:05 -0500
Subject: Update readme

---
 Readme.adoc | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

(limited to 'Readme.adoc')

diff --git a/Readme.adoc b/Readme.adoc
index 798c6fb..ec62be0 100644
--- a/Readme.adoc
+++ b/Readme.adoc
@@ -20,6 +20,14 @@ https://drive.google.com/drive/folders/0B8DUIB5m9fukVHZhX1pRZFhHY2M?resourcekey=
 
 == Tips
 
+=== Incremental development
+
+Many times, compilation or runtime error messages are not helpful or
+borderline cryptic.  Debugging tools help a lot.  But narrowing down what
+component most likely failed is of **great** help.  Develop each "module"
+separately, compile and debug frecuently.  Make sure each "module" works OK
+before beginning the next.
+
 === Debugging
 
 You should definitly make effective use the debugging tools from the IDE
@@ -30,9 +38,6 @@ https://en.wikipedia.org/wiki/LLDB_(debugger)[LLDB], and they share most of the
 basic concepts.  You can https://www.youtube.com/watch?v=Dq8l1_-QgAc[learn the basics] 
 fast and start **practicing**.
 
-(Many times, the compilation or runtime error message is not helpful at all or
-borderline cryptic.  Debugging tools help a lot.)
-
 Prof. Guanira states it clearly in "Guia de Creacion Ejecucion y
 Depuracion.pdf":
 
-- 
cgit v1.2.3

