We should track our decisions in a decision log

When we need to make decisions we may schedule a meeting, or start some POC or just lead by example. We’ll need to properly explain our idea, present pros and cons and communicate it well to all interested parties. A process we’ve been using for this is to create a decision log document.

This is similar in concept to a RFC but the semantics are different. While on a RFC the focus is on how we’re doing something and specific details, the decision log is all about presenting ideas and reach an outcome.

Leveling up developers

As a line manager one of my responsibilities is to level up developers. This is something very challenging that I started to like a lot. I have a primary goal on my 1on1s: how can I level up this person? How can I follow the work that is being done and give good, candid, actionable feedback? How can we know that in fact we’re improving?

This starts by trying to understand what my mentees value and where do they see themselves. I try to do that is by asking:

Imagine that you are 10x more better. What does that look like?

If you love them, let them go!

Once upon a time I had a manager that spent the first two weeks of his then new job going through Excel sheets and meetings with the CEO. I had no idea what was going on, none of us in his team had. He was the first to arrive at the office, said good morning to the rest of us as we walked in, had coffee and some informal chats with us about how things were going and for those two weeks that was pretty much it. There was no bossing around or implementing “disruptive” (please do air quotes while reading for full effect) procedures. At some point we were wondering if he was going to do any actual work at all… ever!

2018 in review

I created this blog almost one year ago. It has been quite a ride. I have shared a lot and I have learned a lot also. I’ve published 50 articles, divided in 30 opinion articles, 13 interviews and the rest are references to videos.

During this year I’ve had +20k unique visitors. My top 5 most visited articles are:

  1. From Rails to Clojure, then to Java, then back to Rails
  2. Code patterns that are a recipe for trouble
  3. My framework for one-on-ones
  4. That project where no one wants to work at
  5. Create an onboarding template

Consultant interview: Erik Dietrich - DaedTech LLC

Erik is the author of DaedTech, a blog about software stories that I follow. He has published several books, being Developer Hegemony: The Future of Labor the latest.

On this interview we discuss topics that go from strategic decisions regarding code bases, guidelines for building software, how to deliver features with quality and how to make developers more valuable.