The CTO and the Zen of Waiting How to Wait for People to Truly Learn In a tech world used to moving at the speed of deploys, we tend to assume that people should evolve at the same pace: new skills in a few weeks, new languages “learned” in a two-day course, new processes absorbed after a single meeting. Reality is different: people grow at their own pace, made of exposure, reflection, attempts, mistakes, setbacks, and new restarts.

Aligning the Technical Team with Business Goals: A Practical (and Honest) Guide Aligning the technical team with business goals is one of the most delicate, frustrating, and strategic responsibilities for anyone leading engineering. This isn’t a theoretical topic: it’s a daily struggle. It’s the recurring doubt of every CTO and Engineering Manager: “Am I communicating the right way? Am I truly conveying the urgency or importance of things?” Even I, after years of technical leadership, often feel like I still haven’t found the perfect formula.

Technical Debt: Understanding It, Managing It, and Turning It into a Strategic Advantage Technical debt is one of the most discussed (and misunderstood) concepts in the tech world. It’s not just about hastily written code or suboptimal choices: it’s a natural dynamic of software development that directly affects the speed, quality, and sustainability of team work. Understanding it is essential not only for those who lead the technical area, but for all C-levels involved in the company’s strategic decisions.

How I Choose a New Technology Without Getting Seduced by the Hype (Confessions of a pragmatic techie in a world full of buzzwords) Every year a new “revolutionary technology” appears, promising to change everything: 10x performance, infinite scalability, zero maintenance, flying unicorns, and maybe even a macchiato on the side. If you’ve been in tech for a while, you know how it goes: the hype cycle ignites, LinkedIn timelines explode, the sales team lights up… and you, who live between Linux, metrics, and late-night incidents, develop instant hives.

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 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.