New chapter: people that care are annoying

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

@@ -78,4 +78,5 @@ template = "section-contentless.html"
 	* [Learn To Say No](say-no)
 	* [Take Responsibility For The Use Of Your Code](responsible-code)
 	* [Don't Tell It's Done When It's Not](not-done)
+	* [People Get Upset About Code And Architecture Quality 'Cause They Care](people-care)
 	* [You'll Learn About Yourself The Hard Way](learn-about-yourself)

content/books/things-i-learnt/learn-about-yourself/index.md

@@ -22,4 +22,14 @@ The worst part of it all? Very few people will tell you what you're doing
 before it's too late -- you'll get in trouble way before you could actually
 understand what you were doing.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/not-done", prev_chapter_title="Don't Tell It's Done When It's Not") }}
+But, again, you'll get in trouble.
+
+And you _must_ learn about these events. Take the feedback as true, even if
+you don't agree with it. I had my falls, and I always took it as something I
+need to improve, even if later I said to my psychologist that I thought it was
+unfair and biased -- mostly 'cause I'm the quiet guy that always took the
+blows and never complained about, and people taking the flak from me were more
+vocal and friendlier to the higher-ups. But, again, I took it as true, and did
+my best to work on those problems.
+
+{{ chapters(prev_chapter_link="/books/things-i-learnt/people-care", prev_chapter_title="You'll Learn About Yourself The Hard Way") }}

content/books/things-i-learnt/not-done/index.md

@@ -30,4 +30,4 @@ On the other hand, if you say "Almost, but there is this thing that bothers me
 and I think it may give us a headache in the future", they will understand. So
 be clear and transparent about your work.
 
-{{ chapters(prev_chapter_link="/books/things-i-learnt/responsible-code", prev_chapter_title="Take Responsibility For The Use Of Your Code", next_chapter_link="/books/things-i-learnt/learn-about-yourself", next_chapter_title="You'll Learn About Yourself The Hard Way") }}
+{{ chapters(prev_chapter_link="/books/things-i-learnt/responsible-code", prev_chapter_title="Take Responsibility For The Use Of Your Code", next_chapter_link="/books/things-i-learnt/people-care", next_chapter_title="People Get Upset About Code And Architecture Quality 'Cause They Care") }}

content/books/things-i-learnt/people-care/index.md

@@ -0,0 +1,22 @@
++++
+title = "Things I Learnt The Hard Way - People Get Upset About Code And Architecture Quality 'Cause They Care"
+date = 2019-07-19
+
+[taxonomies]
+tags = ["en-au", "books", "things i learnt", "personal", "care"]
++++
+
+At some point, you'll describe some solution/decision about some piece of
+code or some architectural design and people will seem annoyed/pissed about
+it.  When people care about a product/code, they do that.
+
+<!-- more -->
+
+Or maybe _you_ will get annoyed/pissed.
+
+I think one of the nicest compliments I ever got was "You're annoying 'cause
+you care" when we left a meeting in which we decided to cut corners and do
+things halfway to beat some deadline -- or just 'cause people were not in the
+mood to do things in a more complete way.
+
+{{ chapters(prev_chapter_link="/books/things-i-learnt/not-done", prev_chapter_title="People Get Upset About Code And Architecture Quality 'Cause They Care", next_chapter_link="/books/things-i-learnt/learn-about-yourself", next_chapter_title="You'll Learn About Yourself The Hard Way") }}