From 71de16cd956c4b683fb3df66857937e3a9e1005b Mon Sep 17 00:00:00 2001 From: Julio Biason Date: Fri, 21 Jun 2019 12:25:28 -0300 Subject: [PATCH] New chapter: Futuring thinking is future trashing --- content/books/things-i-learnt/_index.md | 1 + .../things-i-learnt/future-trashing/index.md | 26 +++++++++++++++++++ .../things-i-learnt/languages-tests/index.md | 2 +- 3 files changed, 28 insertions(+), 1 deletion(-) create mode 100644 content/books/things-i-learnt/future-trashing/index.md diff --git a/content/books/things-i-learnt/_index.md b/content/books/things-i-learnt/_index.md index b73f417..2dbb18d 100644 --- a/content/books/things-i-learnt/_index.md +++ b/content/books/things-i-learnt/_index.md @@ -16,3 +16,4 @@ template = "section-contentless.html" * [Make Tests That You Know How To Run on the Command line](tests-in-the-command-line) * [Be Ready To Throw Your Code Away](throw-away) * [Good Languages Come With Tests](languages-tests) + * [Future Think Is Future Trashing](future-trashing) diff --git a/content/books/things-i-learnt/future-trashing/index.md b/content/books/things-i-learnt/future-trashing/index.md new file mode 100644 index 0000000..dd8ef9c --- /dev/null +++ b/content/books/things-i-learnt/future-trashing/index.md @@ -0,0 +1,26 @@ ++++ +title = "Things I Learnt The Hard Way - Future Thinking is Future Trashing" +date = 2019-06-21 + +[taxonomies] +tags = ["en-au", "books", "things i learnt", "design", "solution"] ++++ + +When developers try to solve a problem, they sometimes try to find a way that +will solve all the problems, including the ones that may appear in the future. + + + +Trying to solve the problems that will appear in the future comes with a hefty +tax: future problems future will never come -- and, believe me, they _never_ +come -- and you'll end up either having to maintain a huge behemoth of code +that will never be fully used or you'll end up rewriting the whole thing +'cause there is a shitton of unused stuff. + +Solve the problem you have right now. Then solve the next one. And the next +one. At one point, you'll realize there is a pattern emerging from those +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") }} diff --git a/content/books/things-i-learnt/languages-tests/index.md b/content/books/things-i-learnt/languages-tests/index.md index e75dc71..2f0d7e1 100644 --- a/content/books/things-i-learnt/languages-tests/index.md +++ b/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") }} +{{ 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") }}