Technical Debt Ratio
Measure the cost to fix code issues relative to development cost. Essential for balancing feature velocity with code health.
Strategic guidance for CTOs on technology decisions, roadmaps, and aligning engineering with business objectives.
11 articles, frameworks, and resources
Measure the cost to fix code issues relative to development cost. Essential for balancing feature velocity with code health.
A comprehensive framework for creating engineering strategy and roadmaps that align technical work with business outcomes. Includes templates for strategy documents, roadmap formats, and prioritization frameworks.
Alpine.js vs Godot: How CTOs Choose Between UI Sprinkles and a Full Game Engine
Build vs Buy Decision Framework: A CTO Guide to Weighted Make or Buy Analysis
Technical strategy under uncertainty: how CTOs make bets without locking the company in
Build vs buy decision framework: how to use a weighted matrix
Ward Cunningham technical debt and the quadrant model
Does the AI revolution change the buy vs build decision?
Most CTOs I meet can describe their calendar, but not their job. That's not a knock-it's just what happens when the role is a moving target.
A technical debt tracking template with categorization, prioritization, and paydown planning for engineering teams.
A structured quarterly planning template for engineering teams with OKRs, capacity planning, and roadmap alignment.
Have experience to share? We welcome contributions from technical leaders.
Learn how to contribute