In this article, you’ll learn how we managed to take decisions at scale at Doctolib, by using the Request For Comment process.

Scaling an engineering team is hard. Very hard. Lines of communication and interactions between teams grow constantly and more than proportionally. Eventually you may find yourself dealing with problems like technology misalignment, lack of visibility and standardisation.

How can you ensure everybody in the team has the necessary visibility and, can participate and contribute to technical discussions? To solve this problem at Doctolib we introduced the Request For Comment process.

What is an RFC?

The RFC system was first introduced by Steve…

What good mentorship looks like

Photo from Wikipedia.

During the past 15 years, I’ve explored different ways to acquire the necessary knowledge and skill to move forward in my growth. Most of my efforts were spent on formal training and courses. I thought it was the way to build up the fundaments of my future. I still believe it was the right thing to do, but I didn’t know I was neglecting one of the most effective learning methods.

I’m a history lover, and a few years ago, I was reading about the Renaissance movement — a cultural revolution that changed the course of world history between the…

The Matrix

When in 2006 I started my career in the tech industry there was a shared opinion spreading into the software engineering community: poor software engineers eventually become managers.

Despite never liking the patronising attitude of the self-declared “real” engineers, I have to say that their opinion was supported by more than just a sense of entitlement. The reality was that most of the managers they worked with were ex-engineers had little hands-on experience in the field or people had a background in non-techonoligical fields, rather than a technological one.

My hope at the time was that, with the natural evolution…

Credit to: ChartMogul

How to transition from the “move fast and break things” paradigm to a “keep a steady pace and don’t break things” — all while making sure you don’t jeopardize customer feedback or time to market.

One of the most exciting and important moments for a product and engineering team is when you grow beyond 2–3 contributors to as many as 10–15. In my experience everyone is full of energy, is positive and is engaged — but with more hands on and ideas on the development lifecycle, there is more room for risks and roadblocks.

Imagine a scenario like this…


Code reviews main goal is to improve our solutions while learning new technologies and techniques. Implement an effective and efficient code review process is not easy. It’s important to not only consider them as a set of tasks and principles, but as a major behavioural change operated through task and principles.

Why Code Reviews?

As with any intellectual work, software has intrinsic inclination towards failure. Code reviews are a way to mitigate failure by:

  • increasing code quality
  • ensuring coding standards
  • validating the implementation
  • sharing knowledge on the areas being changed

What to review?

It’s important to understand that CRs are not a sole responsibility of the…

Marco Ziccardi

Engineering Manager | Kaizen advocate | Music addicted

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store