summaryrefslogtreecommitdiffstats
path: root/Readme.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'Readme.adoc')
-rw-r--r--Readme.adoc11
1 files changed, 8 insertions, 3 deletions
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":