/images/avatar_2026.png

Technical mentoring: how to avoid becoming the team's bottleneck

Technical mentoring: how to avoid becoming the team’s bottleneck Technical mentoring is one of the most delicate and, at the same time, most important aspects within a development team. Helping others grow, sharing experience, giving direction, avoiding mistakes already made: all of this is essential. But there is a hidden risk that anyone who does mentoring knows very well: becoming the team’s bottleneck. If every decision goes through you, if every “hard” problem ends up on your desk, if others wait for your approval before moving forward, you’re no longer a mentor: you’re a single point of failure.

Technical documentation: a journey, not a recipe

Technical documentation: a journey, not a recipe Technical documentation is not a static object, nor a manual you write once and then forget. It’s a journey: it evolves, changes shape, and adapts to the people who need to use it. In my company, I’ve realized that the real challenge isn’t “writing”, but making documentation part of the workflow, instead of a forgotten archive. What follows is not an infallible method, but a set of attempts and practices that over the years have helped me and the teams I’ve worked with turn documentation into real support — not an annoyance.

From Senior Developer to CTO

From Senior Developer to CTO: the career shift no one talks about Everyone loves to describe the transition from Senior Developer to CTO as a natural evolution. Visionary leadership, strategy, innovation, long-term vision. Elegant, reassuring words that ignore the uncomfortable truth: when you become a CTO, you stop doing the job you spent years mastering. It’s not a promotion. It’s a career change. And almost no one prepares you for this shock.

When I Realized I Had Become a Micromanager

When I Realized I Had Become a Micromanager (and Why It Became My Turning Point) I remember the scene perfectly. It was a regular Thursday morning, one of those days when your calendar is just a list of fires to put out and the coffee is never enough. My team was working on a new integration and we had a tight deadline to meet. I was on a call, headset half crooked, one hand on the keyboard, rereading a PR for the third time—the same one I had already corrected five days earlier.

Production Incident Management: My Mental Checklist

Production Incident Management: My Mental Checklist When something goes wrong in production, you need method, clarity, and above all, collaboration. Over time, I’ve developed a mental checklist that helps me move in an orderly way, avoiding impulsive reactions and working in tandem with the team best suited to the situation. In this article, I share my approach to incident management, organized into logical blocks that can be applied in any technical environment.

How I Evaluate a Senior Developer (Beyond Technical Skills)

How I Evaluate a Senior Developer (Beyond Technical Skills) When I evaluate a senior developer, technical competence is only one of the variables—and often not the most important one. A senior developer, by definition, is someone who must be able to impact the team, the processes, and the company. This is why my evaluation method focuses on aspects that go far beyond code. Soft Skills: the real value multiplier Soft skills are the foundation of everything.