I spent 7 years keeping the TAB's mainframes alive. It taught me everything I know about modern IT.

Before I founded DJC in 1999, I spent seven years at Concurrent Computer Corporation. My job was managing the mainframes that ran the TAB, Tattersalls, and systems for the Department of Defence.

Think about what those systems had in common.

If the TAB went down on a Saturday afternoon, it did not go down quietly. Every pub and betting shop in the state knew within a minute. Millions of dollars of turnover stopped. It made the news.

If Tattersalls had a problem on draw night, there was no “we will fix it Monday”. The draw happened when the draw happened.

And Defence systems, I will simply say this: some environments do not accept excuses at all.

Working on those systems taught me three rules, and I have run DJC on them for 27 years.

Rule one: uptime at any cost

On those mainframes, downtime was not an inconvenience. It was a public event with a dollar figure attached, per minute.

So you did not hope things would stay up. You engineered them to stay up. Redundancy was not a line item to trim, it was the whole point. You knew your failure modes before they failed, because you had rehearsed them.

Most businesses today run on systems every bit as critical to them as the TAB’s were to the TAB. If your production line stops, if your practice management system goes down, if your warehouse cannot scan, you are losing money by the minute and trust by the hour. The scale is different. The discipline required is not.

Yet I still see businesses treat uptime as something you buy insurance against rather than something you engineer for. That mindset difference, hope versus engineering, is the single biggest divide I see between businesses that handle a bad day and businesses that get flattened by one.

Rule two: reliability at all costs

Reliability is not the same as uptime. Uptime is whether the system is on. Reliability is whether you can trust what it does, every single time.

A betting system that was up but occasionally miscounted would have been worse than one that was down. Nobody would ever trust it again.

In your business, reliability is the report that is always right, the backup that always restores, the invoice run that never double-charges. It is boring. It is also everything, because your team makes decisions based on what your systems tell them. The day they stop trusting the numbers is the day they go back to spreadsheets and gut feel, and all your IT spend achieves nothing.

Reliability comes from the unglamorous work: testing restores instead of assuming them, monitoring the things that matter, managing systems proactively instead of waiting for tickets.

Rule three: security at all costs

Here is the part that surprises people. We were obsessive about security decades before “cyber” was an industry.

Not because of ransomware, which did not exist in its modern form, but because the systems held money and information that mattered, and because we assumed someone, somewhere, would try. Access was controlled ruthlessly. Changes were reviewed. Trust was never the default.

Today that assumption is simply reality for every Australian business. Someone is trying. The modern security frameworks we align clients to, SMB1001 and the Essential Eight, are formalised versions of the same posture we held on those mainframes: assume hostility, control access, verify everything.

We hold ourselves to the top of that ladder. DJC is certified to SMB1001 Diamond, the standard’s highest tier, alongside ISO 27001 and ISO 9001. I mention it here for one reason: it is the same instinct from the mainframe days. You do not ask a client to meet a standard you have not met yourself.

The tools changed completely. The thinking has not changed at all.

Why this matters when you choose an IT partner

When I started DJC, I made a decision that has shaped the business ever since: I would rather serve fewer clients to that mainframe standard than many clients to an average one.

Twenty-seven years later, our first two clients are still with us. I do not think that is because we are cheap or because we are nice, although I hope we are pleasant enough. I think it is because uptime at any cost, reliability at all costs, and security at all costs is a standard people can feel, even if they never see the machinery behind it.

If your current IT feels like hope rather than engineering, that is worth a conversation.

Book Your Free IT Roadmap Session: thirty minutes with me or Julian. Your cost position, your cyber gaps, your AI opportunities. You keep the roadmap.