Writing on technology leadership, scaling engineering teams, and CTO strategy.
Pull request sizes are up 33%. Change failure rates are climbing nearly 30%. The culprit isn't laziness — it's confidence without context. Why context engineering is the CTO-level discipline that separates rigor from recklessness.
Read more →February 2026 · 10 min readIf you're selling to enterprise, you've heard the question: 'Are you SOC 2 compliant?' Here's what I learned from the SOC 2 journey at Laasy — and the tools that made it manageable.
Read more →February 2026 · 8 min readEvery technical leader knows the feeling: constant requests, endless priorities, and the quiet pressure to say yes to everything. But the most important technical decision is often deciding what not to build.
Read more →January 2026 · 7 min readNearly every startup makes a quiet promise: 'We'll fix it after launch.' What makes this promise dangerous isn't that it's dishonest—it's that it's based on a future that almost never exists.
Read more →January 2026 · 9 min readCTO is one of the most overloaded titles in modern companies. Two people can hold the same title and solve entirely different problems.
Read more →Pull request sizes are up 33%. Change failure rates are climbing nearly 30%. The culprit isn't laziness — it's confidence without context. Why context engineering is the CTO-level discipline that separates rigor from recklessness.
If you're selling to enterprise, you've heard the question: 'Are you SOC 2 compliant?' Here's what I learned from the SOC 2 journey at Laasy — and the tools that made it manageable.
Every technical leader knows the feeling: constant requests, endless priorities, and the quiet pressure to say yes to everything. But the most important technical decision is often deciding what not to build.
Nearly every startup makes a quiet promise: 'We'll fix it after launch.' What makes this promise dangerous isn't that it's dishonest—it's that it's based on a future that almost never exists.
CTO is one of the most overloaded titles in modern companies. Two people can hold the same title and solve entirely different problems.
The most common cause of engineering dysfunction isn't technical debt — it's unclear ownership. Here's how to diagnose and fix it.
Before choosing models or platforms, establish clear governance and success criteria. Most AI initiatives fail due to organizational readiness, not technical limitations.
Technical founders often struggle to delegate effectively. The path forward requires deliberate role design, not just hiring.
Weekly insights on technology leadership, scaling engineering teams, and CTO strategy. No fluff — just lessons from the trenches.