Browse Source

New chapter: Dont say it is done

master
Julio Biason 5 years ago
parent
commit
9261ef6686
  1. 1
      content/books/things-i-learnt/_index.md
  2. 33
      content/books/things-i-learnt/not-done/index.md
  3. 2
      content/books/things-i-learnt/responsible-code/index.md

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

@ -77,3 +77,4 @@ template = "section-contentless.html"
* [Code of Conduct Protect YOU, Not THEM](coc) * [Code of Conduct Protect YOU, Not THEM](coc)
* [Learn To Say No](say-no) * [Learn To Say No](say-no)
* [Take Responsibility For The Use Of Your Code](responsible-code) * [Take Responsibility For The Use Of Your Code](responsible-code)
* [Don't Tell It's Done When It's Not](not-done)

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

@ -0,0 +1,33 @@
+++
title = "Things I Learnt The Hard Way - Don't Tell It's Done When It's Not"
date = 2019-07-18
[taxonomies]
tags = ["en-au", "books", "things i learnt", "personal", "responsibility"]
+++
You are tired of running the same thing over and over again. You kinda
remember that something weird may happen, but because you're tired, you tell
everyone that "It's finished". Don't.
<!-- more -->
I must admit that I've done this. Yes, there is that corner case that I didn't
test. Yes, there is that piece of code that, although it works, it's weird.
Yes, I left a technical debt behind. But we get tired of looking at the same
thing over and over. And we get pushed by higher ups to deliver stuff. And
that's when we say "It's done", when it's not.
Although we just dodged one, we end up leaving our colleagues -- people that
really depend on our work -- down. They expect to connect to whatever we are
doing to keep going. The expect to see the results of their work crystallized
by ours. And they can't. 'Cause we said "It's done" when it wasn't.
And you can be sure, as soon as that happens, they will be the first to point,
in minutes, that it is not done.
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") }}

2
content/books/things-i-learnt/responsible-code/index.md

@ -45,4 +45,4 @@ looking for a new place to work. People on larger and "cooler" companies, like
Google, left their jobs because they didn't agree with what the company was Google, left their jobs because they didn't agree with what the company was
doing, and so can you. doing, and so can you.
{{ chapters(prev_chapter_link="/books/things-i-learnt/say-no", prev_chapter_title="Learn To Say No") }} {{ chapters(prev_chapter_link="/books/things-i-learnt/say-no", prev_chapter_title="Learn To Say No", next_chapter_link="/books/things-i-learnt/not-done", next_chapter_title="Don't Tell It's Done When It's Not") }}

Loading…
Cancel
Save