New chapter: Resist Easy

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

@@ -38,6 +38,7 @@ template = "section-contentless.html"
 		* [Types Say What Your Data Is](data-types)
 		* [If Your Data Has a Schema, Use a Structure](use-structures)
 		* [Don't Mess With Things Outside Your Project](outside-project)
+		* [Resist The Temptation Of Easy](resist-easy)
 * Community/Teams
 	* [A Language Is Much More Than A Language](languages-are-more)
 	* [Understand And Stay Away From Cargo Cult](cargo-cult)

content/books/things-i-learnt/languages-are-more/index.md

@@ -39,4 +39,4 @@ surface of what the whole of a language encapsulates and if you ignore the
 other elements in it, you may find yourself with a cute language in a
 community that is always fighting and never going forward.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/use-structures", prev_chapter_title="If Your Data Has a Schema, Use a Structure", next_chapter_link="/books/things-i-learnt/outside-project", next_chapter_title="Don't Mess With Things Outside Your Project") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/resist-easy", prev_chapter_title="Resist The Temptation Of Easy", next_chapter_link="/books/things-i-learnt/outside-project", next_chapter_title="Don't Mess With Things Outside Your Project") }}

content/books/things-i-learnt/outside-project/index.md

@@ -32,4 +32,4 @@ thing using extensions or actually coding around the problem, even duplicating
 the framework functions, would probably take longer and make you write more
 code, but in the long run, it's worth the time.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/use-structures", prev_chapter_title="If Your Data Has a Schema, Use a Structure", next_chapter_link="/books/things-i-learnt/languages-are-more", next_chapter_title="A Language Is Much More Than A Language") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/use-structures", prev_chapter_title="If Your Data Has a Schema, Use a Structure", next_chapter_link="/books/things-i-learnt/resist-easy", next_chapter_title="Resist The Temptation Of Easy") }}

content/books/things-i-learnt/resist-easy/index.md

@@ -0,0 +1,31 @@
++++
+title = "Things I Learnt The Hard Way - Resist The Temptation Of Easy"
+date = 2019-07-01
+
+[taxonomies]
+tags = ["en-au", "books", "things i learnt", "ides"]
++++
+
+Sure that IDE will help you with a ton of autocomplete stuff and let you
+easily build your project, but do you understand what's going on?
+
+<!-- more -->
+
+I'm not denying the fact that IDEs make things easier. The fact is, you should
+not rely heavily on their features.
+
+I mentioned before that you should at least know how to [run tests on the
+command line](/books/things-i-learnt/tests-in-the-command-line) and the same
+applies to everything in IDEs: how to build, how to run, how to run tests and,
+let's be honest here, how to find proper names for your variables and
+functions. 'Cause, sure, it's nice that the IDE can complete all the names of
+the functions, but if the autocomplete feature was off, would you know which
+function you need? In other words, have you thought at least 10 seconds about
+a good name for your function so you _won't_ need to use autocomplete to
+remember its name?
+
+These days, IDEs can autocomplete almost everything, from function names to
+even how to name your variables. But using the autocomplete is not always a
+good solution. Finding better names is.
+
+{{ chapters(prev_chapter_link="/books/things-i-learnt/outside-project", prev_chapter_title="Don't Mess With Things Outside Your Project", next_chapter_link="/books/things-i-learnt/languages-are-more", next_chapter_title="A Language Is Much More Than A Language") }}