AI accelerates output but not judgment. Quality must be engineered deliberately in an era where most code is machine-generated.
Bad software is rarely the result of weak engineers. It is the result of weak management decisions.
The definition of good software has split into two realities. Most leaders still haven’t realized it.
From AWS outages to Germany’s Telematikinfrastruktur, 2025 showed that resilience isn’t built in data centers — it’s enforced by leadership that understands complexity and owns interdependencies.
AI-created micro-apps are creating technical debt faster than ever, while eroding the very skills that make engineering teams valuable. How do CTOs shift from managing execution to managing decision quality at scale?
It’s 2025, 12 years after “The Phoenix Project”. Yet, there are companies that seem to be unaware of product and development culture.
On the fundamental difference between a leader and a manger, and why it is a good thing to have both.
Looking at different leader types from military, business and tech - and why they’re called leaders.
Three years later, data confirms that stepping back from leadership wasn’t retreat — it was strategic repositioning.
Vision gives direction, mindset defines motion. The team turns both into reality. Building the right crew is the CTO’s most important design decision.
A CTO’s true influence begins long before code is written. It lies in shaping a clear vision and the company mindset that turns that vision into motion.
Walking the thin line between being an executive, tech lead and human being in a company.