I'm an engineer and builder in Brisbane. Most of my work happens in the gap between what a product wants to be and what the code will allow, and this is where I write down what that gap teaches me. What makes it worth reading is the judgement, not a CV.
Years in ecommerce and engineering, founder of an Australian SaaS, and a fractional engineering advisor to teams in regulated industries. Everything here comes out of doing the work, not theorising about it. I ship, I lead, and I sit with the same hard problems my readers do. When a thought finally gets heavy enough to be worth saying once and saying properly, it becomes a post.
A lot of it circles the same territory: building without a team around you. I went solo after years on teams and found the parts no one warns you about: the lost calibration, the silence where feedback used to be, the momentum you have to manufacture on purpose. I write the thing I wish someone had told me plainly at the time.
I use Australian spelling, contractions, and short sentences. I try not to sound like a press release, because I'm not one. No hype, no hustle, no funnels. Just the clearest version of a thought I can manage.
For first-time technical founders. The hard version of what code can and can't do for a young company, and what to actually do about it this week.
For engineering leaders. How to hold a standard without holding every decision, and why reaching for control is usually the more expensive choice.
For heads and directors weighing their next move. Choosing a position from judgement, like someone who has decided, not a candidate hoping to be chosen.
For solo builders. Isolation, calibration, and momentum no one is watching: the parts of going solo that nobody warns you about.
I help regulated Australian teams in health, government, finance, and aged care adopt AI deliberately: where it earns its place, where it doesn't, and how to ship it under audit. Fractional engineering advisory, scoped to the decision in front of you.
If that's the problem on your desk, [email protected].
Occasional, when a piece is worth your time. Unsubscribe anytime.
Most of what's here began as a conversation I realised I kept having, with a founder, a tired lead, someone building alone. The blog is where those answers finally get written down properly, so the next person doesn't have to ask. If a piece helps you think more clearly about the next decision, it has done its job.