Tag Archives: technical debt
Technical Debt Management — Staying Fast Without Breaking Things Over Time
Vibe coding produces technical debt faster than traditional development. That is a property of the methodology, not a failure of execution. Managing it systematically is what determines whether the practice is sustainable over years or collapses under accumulated debt within eighteen months.
The Honest Risk Assessment — What Can Actually Go Wrong With Vibe Coding
Vibe coding has real risks: technical debt, security gaps, skill atrophy, over-reliance on one AI provider, and knowledge concentration. This post names them clearly and describes what to do about each one — without either dismissing them or treating them as dealbreakers.
The Duplicate Code Problem — Building the Same Thing Seven Times
The most expensive mistake in the portfolio: building the same API clients and database classes independently in product after product, when a shared library should have existed from product three. How it happened, what it actually cost, and the rule that prevents it.