What a Technical Due Diligence Actually Finds
Buying a software business means buying its codebase. Here is what a technical due diligence looks for, what it can and cannot tell you, and when it is too late to run one.
Seven Questions to Ask Any Integration Partner Before You Sign
Most integration projects fail on maintenance, not build. Seven questions that separate a partner who will still be useful in year two from one who will not.
The Vibe-Coded App Runs. That Doesn’t Mean It’s Safe.
AI built the app and it runs. Here is what a rescue actually checks first, why generated code fails in consistent places, and why starting again is usually the expensive answer.
Laravel 9 to 12 in Two Weeks: the Part That Was Not the AI
A major-version Laravel migration on a large codebase took two weeks. The duration is not the technique. Here is the order of operations that made it possible.
Getting Your Nights Back: AI for Quoting, Invoicing and Job Admin
Most tradies lose their evenings to quotes and invoices. Here is what AI can genuinely take off your plate, what it cannot, and how a setup session works.
Why the AI Gets Worse as Your Codebase Gets Bigger
A large codebase makes an AI assistant slower, not faster, because the model cannot hold it. PIM, for Prompt, Iterate, Modularise, is the habit that keeps code small enough for the machine to reason about.






