New chapter: hero projects

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

@@ -70,6 +70,7 @@ template = "section-contentless.html"
 	* [Code Formatting Tools Are Ok, But No Silver Bullet](code-formatters)
 	* [Code Style: Follow It](code-style)
 	* [... Unless That Code Style Is The Google Code Style](google-code-style)
+	* [Hero Projects: You'll Have To Do It Yourself](hero-projects)
 * Personal
 	* [Companies Look For Specialists But Keep Generalists Longer](specialists)
 	* [Keep A List of Stupid Bugs That Took More Than 1 Hour To Solve](stupid-bugs-list)

content/books/things-i-learnt/google-code-style/index.md

@@ -16,4 +16,4 @@ The only reason to use Google Code Style is in case someone less smart than
 you decided it would be a good idea to use it. Then, I feel sorry for you, but
 you'll have to follow Google Code Style.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/code-style", prev_chapter_title="Code Style: Follow It", next_chapter_link="/books/things-i-learnt/google-code-style", next_chapter_title="... Unless That Code Style Is The Google Code Style") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/code-style", prev_chapter_title="Code Style: Follow It", next_chapter_link="/books/things-i-learnt/hero-projects", next_chapter_title="Hero Projects: You'll Have To Do It Yourself") }}

content/books/things-i-learnt/hero-projects/index.md

@@ -0,0 +1,31 @@
++++
+title = "Things I Learnt The Hard Way - ... Unless That Code Style Is The Google Code Style"
+date = 2019-07-25
+
+[taxonomies]
+tags = ["en-au", "books", "things i learnt", "community", "teams", "hero project"]
++++
+
+An "hero project" is a project/spec change that you personally think will
+solve a group of problems in your project. It could be a different
+architecture, a new framework or even a new language.
+
+<!-- more -->
+
+Hero projects happen mostly when a single developer wants to prove something
+without the support of the company or even the time they are in.
+
+On those projects, developers will spend their free time to write a
+proof-of-concept, just to prove a point.
+
+And, sometimes, it just proves that they are were wrong.
+
+(Although that last point sounds a bit sad, if you have to do an hero project,
+you'll still learn something new and, maybe, even add a new bullet point to
+your CV.)
+
+Just to be clear: Sometimes an hero project will fail [because the answer is
+obvious](/books/things-i-learnt/right-tool-obvious). Don't let that make you
+feel down.
+
+{{ chapters(prev_chapter_link="/books/things-i-learnt/google-code-style", prev_chapter_title="... Unless That Code Style Is The Google Code Style", next_chapter_link="/books/things-i-learnt/specialists", next_chapter_title="Companies Look For Specialists But Keep Generalists Longer") }}

content/books/things-i-learnt/specialists/index.md

@@ -40,4 +40,4 @@ in C show up and guess who also knew C?
 
 [^1]: ... which led me into some sad times when I was working with Python.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/google-code-style", prev_chapter_title="... Unless That Code Style Is The Google Code Style", next_chapter_link="/books/things-i-learnt/stupid-bugs-list", next_chapter_title="Keep A List of Stupid Bugs That Took More Than 1 Hour To Solve") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/hero-projects", prev_chapter_title="Hero Projects: You'll Have To Do It Yourself", next_chapter_link="/books/things-i-learnt/stupid-bugs-list", next_chapter_title="Keep A List of Stupid Bugs That Took More Than 1 Hour To Solve") }}