Articles

#30  Worrying too much in advance

As an engineer, if I have to pick something that I always struggle with, and seems like a never-ending problem, it's worrying too much upfront about an issue that hasn't happened yet, and probably never will.

Read full article

#29  Evolving the Legacy

One of the benefits of working in product companies is watching your product evolve, nevertheless, that road won’t be only a matter of innovation but avoid things turning into impossible to mature legacy systems.

Read full article

#28  Mixing leadership, delegation, and accountability

When we start growing and moving through the laddering of promotions or switching teams, we start experiencing different types of

Read full article

#27  The flaws of the interview process

Over the years there have been changes in the way interview processes are handled, which I believe are causing interviews to evolve into something unnecessarily complicated.

Read full article

#26  Living with a low-profile

Since I can remember I have been afraid to say that I am good at something. Not because I am modest, not because I am humble, it just doesn't come up.

Read full article

#25  Make your own path

At the beginning of your career, following your path can be more important than you think, especially if you tend to reflect on other people's experiences.

Read full article

#24  When autonomy becomes a silo

Ever since I started to work in this field, I have seen a transformation in the way companies shape their teams.

Read full article

#23  A letter to a younger me

This is a short letter that I would like to send to a younger me, who is frustrated finishing a degree in computer science and trying to land his first job in the IT industry.

Read full article

#22  Avoid falling into the building trap

As a developer, if you only look at a list of requirements to follow, building software products can look simple.

Read full article

#21  Think outside the box

Since I started to work in the IT field, there were two stories/analogies that marked me in the way I see software as a process, mainly because there were real-life situations.

Read full article
Load More