Insights
Technical thinking as public evidence of judgement.
Architecture, technical due diligence, AI-accelerated engineering and the difference between software that works and software that can be trusted.
A Working MVP Is Not the Same as a Technology Asset
A product can demonstrate demand while still hiding architectural uncertainty, operational fragility and assumptions that have never been tested at scale.
Read insight → Investors · AI · 5 minAI Has Changed What Investors Should Ask About Software
Why sophisticated product surface is weaker evidence of technical maturity than it used to be.
Read insight → Engineering leadership · 6 minMore Code Is No Longer the Scarce Resource
The bottleneck is shifting from implementation capacity to judgement, control and coherent models.
Read insight → Founders · AI · 6 minWhat Founders Should Verify Before Scaling an AI-Built Product
Questions that become material when velocity begins creating structural responsibility.
Read insight → Financial systems · 6 minWhy Passing Tests Does Not Prove Financial Correctness
Tests can validate paths without proving system-level invariants under failure and concurrency.
Read insight → Architecture · Risk · 6 minTechnical Debt vs. Material Business Risk
A useful distinction between ordinary imperfection and liabilities that constrain business decisions.
Read insight → Scale · Architecture · 6 minThe Architectural Decisions That Become Expensive Only After You Succeed
Why some early choices remain invisible until volume, teams and dependencies compound.
Read insight → Decision making · 6 minWhy Independent Technical Judgement Matters Before an Irreversible Decision
The value of separating evidence from delivery incentives when the stakes are high.
Read insight →