M&A Technical Due Diligence: What CTOs Are Actually Supposed to Do
Most M&A due diligence checklists are written by people who've never opened a terminal. Here's what technical due diligence actually looks like when a CTO runs it.
Thoughts on DNS, engineering leadership, and twenty years of building teams and shipping products.
I write about pragmatic engineering, DNS, cloud infrastructure, and tech leadership. Subscribe via RSS or follow me on LinkedIn to get new articles.
✉ An email newsletter is coming. In the meantime, RSS is the most reliable way to follow along.
Most M&A due diligence checklists are written by people who've never opened a terminal. Here's what technical due diligence actually looks like when a CTO runs it.
Ramadan is my favourite month of the year. Four concepts from my faith that have quietly shaped how I work for the past twenty years — Islamic in origin, universal in application.
I wrote this in 2011. The four tools are the same. My understanding of them isn't.
Most engineers don't hit a skills ceiling. They hit an exposure ceiling — and never realize it.
Most team dysfunction traces back to one thing: leaders who delegate before they've finished thinking. Vague instructions aren't trust — they're just unfinished work passed downstream.
Promotions are a trap disguised as a reward. The Peter Principle isn't about incompetence — it's about a system that punishes people for being exactly what they are.
DNS troubleshooting made practical. Every query I kept reaching for at EuroDNS, explained with real output.
New to the domain name industry? A clear explanation of what domain names are, how they work, and what happens behind the scenes.