I'm John. I've been writing production code since 2005.

I'm a freelance developer in South Africa. For twenty years I've built the things businesses actually run on — payment integrations, lending platforms, document systems, commerce portals, internal tools nobody outside the company will ever see.

A lot of that work has come through agencies. Flume, Getglow and Kallima have handed me client development for years, which means my code has shipped under other people's brands for Woolworths, Nimue and EasyEquities. Agencies bring in a contractor when the work has to hold up and they can't afford to find out later that it doesn't. That is a specific kind of trust and I've built a career on not spending it.

The rest has come direct: a will management platform that ran for four years before being sold to an insurance consortium, a loan origination integration spanning seven lenders, training and commerce sites for South African businesses that needed the thing to work more than they needed it to win an award.

What I'm actually good at

Deciding what not to build. Most of the value I add on a project happens in the first week, when I'm arguing about scope — the feature that duplicates something a third party already does, the caching layer that's a compliance problem waiting to happen, the rewrite of a system that works fine and is merely old.

After that it's unglamorous: modelling data properly, handling failure explicitly, and writing logs that name the thing that broke. That's the difference between a system you maintain and a system you eventually replace. One of my clients said I gave honest input on features even when it went against my financial interest. That's the job.

On AI, since you'll ask

I build with AI tooling and I'm direct about it. It's collapsed the time that scaffolding, boilerplate, fixtures and first-pass integration code used to eat — which is why work an agency quotes at twelve weeks lands in three or four. It has not changed the part that decides whether a system survives: knowing what to build, how the data should be shaped, and what happens when a third party returns something nobody expected.

You're not buying generated code. You're buying twenty years of judgement, applied at a speed that wasn't available a few years ago, with every line reviewed and owned by me.

How I work

Fixed price, agreed in writing before I start. Weekly working demos on a staging URL you can click, so there's never a four-week silence followed by a surprise. You own the code, the repository and every credential from the first commit — I don't hold hosting or source as leverage, and if you want to move to another developer I'll help with the handover.

And I reply within an hour during business hours. It sounds like a small thing. Ask anyone who's waited four days for an agency to answer a one-line question.