Scalability, Sure… But at What Cost? The Real ROI of Distributed Architectures In recent years I’ve seen more and more companies chasing distributed architectures as if they were a badge of modernity: microservices everywhere, queues and streams for everything, three layers of caching, five different databases, and an architecture diagram that looks more like abstract art than an information system. The problem is that complexity always has a price. Not just in infrastructure, but in people, processes, incidents, and time-to-market.

Kind on Rootless Docker Does Not Work on openSUSE Leap Full analysis of the “Delegate=yes” issue and the definitive solution In this article I analyze a real case on openSUSE Leap where kind fails during the creation of a Kubernetes cluster using rootless Docker, showing the well-known error: ERROR: failed to create cluster: running kind with rootless provider requires setting systemd property "Delegate=yes" The message seems to indicate that Delegate=yes is not configured, but the real issue is deeper: cgroup controller delegation.

Reducing Complexity Without Reducing Ambition: Practical Principles for Simpler Systems Because complexity is not an achievement it’s a warning sign. Complexity Is Not Competence: It’s a Warning In our industry, there’s a strange fascination with complexity. We worship it, justify it, and use it as a business card. As if creating something hard to understand were a sign of genius. Spoiler: it isn’t. A complex system is not a masterpiece. It’s an early warning often ignored that foreshadows slowdowns, bugs, rising costs, and increasingly sluggish decision-making.

The Three Habits That Keep Me Clear-Headed as a CTO Being a CTO is not a sport for the faint of heart. The really important decisions often arrive: with incomplete information, under pressure, in the middle of notifications, meetings, and technical surprises. For a while I thought the answer was “just work more and harder.” Then I realized something simple, but uncomfortable: If I don’t protect my mental clarity, I’m sabotaging my own work.

Incident Commander How to train and grow new Incident Commanders in your team When a serious incident happens, it’s not just about CPU at 100%, 500 errors, or exploding queues. There is always another factor at play: the team’s ability to stay clear-headed. At the center of that ability there’s a key figure: the Incident Commander. This article is for those who want to grow new Incident Commanders in their team, defining a training path that is clear, repeatable, and above all, human.

How to Build Antifragile Teams in Digital Chaos In a tech context made of tight deadlines, continuous releases, production incidents, and roadmaps that change every three sprints, the real difference is not made by the “perfect team” but by the team that absorbs shocks, learns fast, and comes back every time a bit stronger. This article aims to present a resilient and modern managerial vision, where the role of the CTO and team leaders is not to eliminate errors, but to design human and organizational systems that can metabolize them.