Builder of products, systems, and strange ideas.
Brisbane-based and product-focused, I like the whole problem: product calls, frontend, backend, AI-assisted workflows, and the weird bits in between that decide whether something actually survives contact with reality.
I like building end to end. Figuring out the real problem, choosing the right shape, wiring it up properly, and staying with it until it survives real use. That is the fun part.
Age 13 / high school
It started with Lego robots and a toolkit challenge win, then turned into a Skyrim wiki that scored an A+. I liked code more than essays, more than equations, and more than anything else I was being asked to do.
Griffith University / Bachelor of Information Technology
University started badly. I was in full party mode, dealing with personal issues, and got the email saying that one more failed course meant I was done. That snapped me awake. I locked in, averaged a 6.75/7 GPA, won Griffith University's Academic Improvement Award, and took home the $3000 prize.
Freelance and indie work
I got made redundant at Dominos and had a choice: go work at another store or actually give software a real crack. I chose the second one. That stretch became four websites, two apps, and my first paid work building a site that genuinely changed a mate's business.
Software Engineer / agency life
That era was hard work, heavy context switching, and the occasional rude startup founder, but the growth was explosive. It was the first time I was trusted to build properly inside real products instead of just theory.
Simpro
For the first time, I was surrounded by seriously smart people. That changed everything. It pushed my growth harder than anywhere else, and it's where I became the guy people trust with weird, ambiguous, research-heavy problems that need good judgment before code.
These days I work across product, frontend, backend, docs, AI-assisted workflows, and the awkward research-heavy stuff that needs good judgment before anyone starts pretending the code is the hard part.
The work I enjoy most usually starts out vague, messy, or slightly cursed. That is normally a good sign. Those are the problems where product judgment and technical range actually matter.
A lot of software work is not about heroics. It is about finding the right shape early enough that the whole thing does not drift into nonsense six weeks later.
Docs, workflows, release confidence, search, automation. I care about the surrounding system because it changes how fast people can move and how often they get stuck.
I led a messy dependency rescue on an aging product, moved it onto modern tooling, handled a major component-library upgrade, and left the platform in a state where future work could breathe again.
I rebuilt an outdated documentation experience, forked the underlying tooling, and added global search by hand so developers could actually find what they needed without guessing.
The interesting problems are usually vague at the start. I built a reputation by taking those on, cutting through the ambiguity, and landing on solutions that make sense before the code ever tries to show off.
An AI-powered goal-setting app that turns a conversation into a real plan, timeline, and trackable progress system.
Trendsetter is the clearest expression of where my work is heading: product-first, full-stack, and built around momentum. You talk to the system about what you want to achieve, it turns that into structure, and then the app makes the journey measurable instead of fuzzy.
A full-stack ecommerce rebuild born from a forced rebrand (lawsuit), with a stronger product and a sharper technical foundation on the other side.
Picklewear is proof that I can build the whole thing. Storefront, admin tooling, payments, sync workflows, deployment flow, search, product ops, and the usual pile of edge cases that only show up when real people are using the system.
Good software dies quickly when it solves the wrong thing beautifully. I would rather pick the right shape than brute-force the wrong one.
I am comfortable moving from product conversations to APIs, UI, deployment, and the occasional production gremlin hunt without changing personality.
Dragging old systems into the present is fun. Doing it without breaking trust is the real skill.
I use AI to tighten loops, gather context, and validate work faster. The thinking was there long before the tooling showed up.
I like sharp systems and good people. The best work usually happens when both are in the room at the same time.
I like meeting people who care about what they build. Founder, recruiter, engineer, curious human, all good. If the conversation is interesting, I am in.