Usually we know RFCs from IETF. It’s that document that for example starts to present the HTML spec. But on this article I’m talking about RFCs (request for comments) in a broader sense. Like a tool that can be used by product/engineering teams to better plan and be productive.

I believe we can split work into two categories: creative work, and regular work. To have a healthy work day we should be able to do both. But regular work is much easier and less demanding. I think both of them can be productive but working smart yields the best results mid to long term.

Getting the best out of my team is one of my responsibilities. For that I need personal time with each teammate. But taking the most out of these sessions can be very hard. So I started to build a framework to help me.

It’s easy to have a sense of how satisfied we are. But sometimes it’s very tricky to clearly say why we are or are not satisfied at work. So I try to translate satisfaction into several specific topics.

Being on call can be daunting. Anything can happen in production and we may be all alone and completely out of our comfort zone dealing with a problem we have no clues about, and with the pressure of having the app down and impacting the business.