Who's actually building your software.
Bloody Good Software is the software practice of Cameron Carmody, based in Sydney. Right now "we" is Cameron. If a project ever needs more hands, you'll know exactly who they are before they touch your code.
Cameron spent nearly a decade inside enterprise technology, across cybersecurity, integration platforms and open-source infrastructure for ANZ enterprises and public-sector teams. That background matters because most software projects fail before the code starts. The real work is understanding the workflow, the buyer, the risk, the handoff, and what done actually means.
AI coding tools have changed the economics of small software projects. They have not changed the need for judgement. We still make the product decisions, write the specs, and decide what should and should not be automated. The tools accelerate the build.
More about Cameron, his writing and his own products lives at cameroncarmody.com.
Spec before code.
Every useful build starts as a written spec. What are we building? Why does it matter? What is out of scope? What does done look like? AI can produce code quickly, but it cannot own those decisions.
Keep the system understandable.
We prefer boring, mainstream technology that a competent developer can inherit: clear database, clear deployment, clear logs, clear ownership. The goal is software you can trust, not software that impresses another engineer.
Get real usage early.
The wealth advisory portal had a paying client using it thirty days after the project started. Real usage teaches faster than private polishing.
Working through something similar?
Tell us about the workflow and what currently breaks. We'll tell you straight whether it's worth building.