Reorganized the index, with better sub-topics

content/books/things-i-learnt/_index.md

@@ -7,16 +7,20 @@ template = "section-contentless.html"
 * [Intro](intro)
 * [Disclaimer](disclaimer)
 
-* Programming:
+* Programming
-	* [Spec First, Then Code](spec-first)
+	* Before you start writing code...
-	* [Write Steps as Comments](steps-as-comments)
+		* [Spec First, Then Code](spec-first)
-	* [Gherkin Is Your Friend to Understand Expectations](gherkin)
+		* [Write Steps as Comments](steps-as-comments)
-	* [Unit Tests Are Good, Integration Tests Are Gooder](integration-tests)
+		* [Gherkin Is Your Friend to Understand Expectations](gherkin)
-	* [Testing Every Function Creates Dead Code](tests-dead-code)
+	* Testing Software
-	* [Tests Make Better APIs](tests-apis)
+		* [Unit Tests Are Good, Integration Tests Are Gooder](integration-tests)
-	* [Make Tests That You Know How To Run on the Command line](tests-in-the-command-line)
+		* [Testing Every Function Creates Dead Code](tests-dead-code)
-	* [Be Ready To Throw Your Code Away](throw-away)
+		* [Tests Make Better APIs](tests-apis)
-	* [Good Languages Come With Tests](languages-tests)
+		* [Make Tests That You Know How To Run On The Command Line](tests-in-the-command-line)
-	* [Future Thinking Is Future Trashing](future-trashing)
+		* [Good Languages Come With Tests](languages-tests)
-	* [Documentation Is a Love Letter To Your Future Self](document-it)
+	* Documentating your code
-	* [The Function Documentation Is Its Contract](document-is-contract)
+		* [Documentation Is A Love Letter To Your Future Self](document-it)
+		* [The Function Documentation Is Its Contract](document-is-contract)
+	* Writing code
+		* [Be Ready To Throw Your Code Away](throw-away)
+		* [Future Thinking Is Future Trashing](future-trashing)

content/books/things-i-learnt/document-is-contract/index.md

@@ -34,4 +34,4 @@ whatever you initially said your function would do -- so the correct solution
 would be to add a new function with a proper contract -- and probably a better
 name.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/document-it", prev_chapter_title="Documentation Is a Love Letter To Your Future Self") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/document-it", prev_chapter_title="Documentation Is a Love Letter To Your Future Self", next_chapter_link="/books/things-i-learnt/throw-away", next_chapter_title="Be Ready To Throw Your Code Away") }}

content/books/things-i-learnt/document-it/index.md

@@ -25,4 +25,4 @@ I have some bad news for you...
 
 [^1]: Please, don't make me revise this in 2027... :(
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/future-trashing", prev_chapter_title="Future Thinking is Future Trashing", next_chapter_link="/books/things-i-learnt/document-is-contract", next_chapter_title="The Function Documentation Is Its Contract") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/languages-tests", prev_chapter_title="Good Languages Come With Tests", next_chapter_link="/books/things-i-learnt/document-is-contract", next_chapter_title="The Function Documentation Is Its Contract") }}

content/books/things-i-learnt/future-trashing/index.md

@@ -23,4 +23,4 @@ solutions and _then_ you'll find your "solve everything". This pattern is the
 _abstraction_ you're looking for and _then_ you'll be able to solve it in a
 simple way.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/languages-tests", prev_chapter_title="Good Languages Come With Tests", next_chapter_link="/books/things-i-learnt/document-id", next_chapter_title="Documentation Is a Love Letter To Your Future Self") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/throw-away", prev_chapter_title="Be Ready To Throw Your Code Away") }}

content/books/things-i-learnt/languages-tests/index.md

@@ -22,4 +22,4 @@ testing framework in their standard library may have options with better
 support and easier access but, again, when they are there from the start, the
 start is better and the final result is better.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/throw-away", prev_chapter_title="Be Ready To Throw Your Code Away", next_chapter_link="/books/things-i-learnt/future-trashing", next_chapter_title="Future Thinking is Future Trashing") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/tests-in-the-command-line", prev_chapter_title="Make Tests That You Know How To Run On The Command Line", next_chapter_link="/books/things-i-learnt/document-it", next_chapter_title="Documentation Is A Love Letter To Your Future Self") }}

content/books/things-i-learnt/tests-in-the-command-line/index.md

@@ -34,4 +34,4 @@ you have no idea how those things "happen", you'll need the help of someone
 else to actually build this kind of stuff, instead of having the knowledge
 (well, half knowledge, the other half is the CI tool) with you all the time.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/tests-apis", prev_chapter_title="Tests Make Better APIs", next_chapter_link="/books/things-i-learnt/throw-away", next_chapter_title="Be Ready To Throw Your Code Away") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/tests-apis", prev_chapter_title="Tests Make Better APIs", next_chapter_link="/books/things-i-learnt/languages-tests", next_chapter_title="Good Languages Come With Tests") }}

content/books/things-i-learnt/throw-away/index.md

@@ -35,4 +35,4 @@ solves the problem, but also the tests for that code.
 ... unless you focus mostly on [integration
 tests](/books/things-i-learnt/integration-tests).
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/tests-in-the-command-line", prev_chapter_title="Make Tests That You Know How To Run on the Command line", next_chapter_link="/books/things-i-learnt/language-tests", next_chapter_title="Good Languages Come With Tests") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/document-is-contract", prev_chapter_title="The Function Documentation Is Its Contract", next_chapter_link="/books/things-i-learnt/future-trashing", next_chapter_title="Future Thinking Is Future Trashing") }}