Zero bug policy

Bugs are a tricky subject. We all write code with bugs and they have a considerable impact on our productivity and on the value added by our deliverables. So we come up with several strategies to handle the bug stream and have a ongoing effort to balance bug house keeping and new features.

I’m a big advocate for a zero bug policy. This means that we should usually have 0 registered bugs. Whenever I present this idea I’m met with skepticism. This is seen as an utopia and not possible. My impression is that developers interpret in a way that would generate punishment when new bugs are added.

But that is not the point. The point is to embrace that we’ll always have bugs, but also aim for a process that will minimize as much as possible the amount of bugs we produce. This will make us leave our comfort zone and question our beliefs.

It’s not about “writing code that never has bugs”. It’s more about “what do we need to change in our day to day work to minimize bugs”.

Product manager interview: Sofia Gonçalves - Resolver

Sofia Gonçalves is a product manager currently working for Resolver.

In this article we talk about what are the responsibilities of a product manager and what are their biggest challenges (for example, defining priorities).

About what’s a good process for product managers and how to deal with partially remote teams.

We also talk about recruiting and mentoring product managers.

The power of abstractions

The other day I was doing a code review and noticed that a mechanism for i18n was added to a new project we’re working on. There was a line like this:

{ key: 'something',
  label: i18n.t('something'),
  value: i18n.n(user.salary, 'currency')}

This is very simple and common I’d say. Even so I left, as I so usually do, a suggestion as a comment:

Suggestion: wrap i18n.t and i18n.n in an abstraction that we control.

Recruiter interview: Goncalo Sequeira - Mercedes-Benz.io

I met Gonçalo Sequeira at a previous company we worked at. He recruited me and because of that I got to interact with him during my full recruitment process.

I learned a lot with him. Soon after he left to boot Mercedes-Benz.io development’s hub in Portugal and I’ve been following his career and still trying to learn from him.

In this interview we cover what’s like to start a development hub, how to recruit the first people and what’s important about them.

Manager interview: Pedro Santos - AMA

These are my replies to my first AMA (ask me anything).

It’s interesting how this made me think and clarify many ideas. I’ve left the AMA format open and added the Ask me Anything page that has instructions on how to receive more questions.

On this interview I give my opinion on several topics regarding engineering management, problems I’ve faced and how they changed me, how to measure performance, how to organise my time and about leadership.