How can we know if we’re learning enough? Or if we’re learning the right things? How can we get some help and find mentors?

Nuno Silva is the first guy I remember meeting when I started at ISEL. We’ve been friends ever since. We’ve done most of the course together, we started Orion’s Belt as a school project and worked at the same companies on our first years as developers.

At some point we parted ways and gained different experiences in different fields. But practically at the same time we started leading teams and trying to be better at it. He’s usually my advisor whenever I have some tricky situation to attend to.

In this interview I try to get some insights on how Nuno works and some best practices on leading teams.

He also contributed to the blog with a guest post:

• Scaling engineering teams

In part 1 we went through several patterns related with writing code that is more maintainable. This article focus on code patterns in testing and also concerning readability and style.

Sometimes I notice that I have just wasted one hour or so because of some bug in my code, or something that I did wrong. When that happens I try to step back, understand what I did and try to come up with a change in my way of working that will prevent it from happening again.