Legacy system

And if you have in the case of this one in Medicare, make sure if you've got old legacy systems or websites with old portal pages, just make sure you take them down.

The government has also acknowledged that the portal itself was a legacy system.

Katie Gallagher says the website was already being moved to a different platform and will not be reactivated.

It is a legacy system, you know, and it is being moved to data.gov.au, so we won't be reactivating it.

But there is protections associated with that.

This is unprecedented activity, so there are...

You're going to kill it.

Yeah, legacy systems, they make the world go round, but at some point in time, they might start to get some termites.

Yeah, yeah, yeah.

That's how it'll be like.

It's completely unbelievable when you come across it for the first time.

But I think it's probably true to say that if you look at the barriers to this happening, you know, 70%, if you sort of go on to post 29 of the report, chart 14, and they say, what are the biggest blockers for intraday repo for that particular use case? They say 70% rate legacy integration with legacy systems as the biggest barrier to intraday repay moving forward.

The actual physical

booking system, sometimes with a tri-party or a CSD, like a clearings house, to use layman's terms, I suppose creates the sort of barrier because this is how it's always been done.

The required for innovation has to occur.

So the...

The legacy systems are a barrier to entry.

But the other one that you mentioned there, Egon, the 24-7 operational model is still an issue.

I would say two technical books that I've...

I think I'm going to skip over a couple of books, but two technical books that I think I highly recommend to everyone are Game Programming Patterns and Working with Legacy Code.

Working with Legacy Code often surprises people as one of my favorite books of all time, but I found it really wonderful when I'm just like plopped into like a monstrous code base.

How do you sort of like quickly make sense of it? And like what are good design patterns to make codes like simpler and easier to reason about? I think...

A lot of my contributions in past projects has been going into a complicated code base and understanding it and then figuring out how to develop features more quickly on top.

And this is by far the hardest job in software development.

What separates the experienced software developer from a beginning software developer is how they handle legacy code.

Can you read somebody else's code, hopefully somewhat well documented? Often not.

make sense of it, understand it enough so you can identify the problem and fix it.

Yeah, Patrick, I'm going to stay with you and shift it slightly here, because only between 15% and 20% of CFOs have actually fully embedded AI into their operations, though that number is up from less than 1% last year.

So as a CFO yourself, why is there a gap between ambition and implementation? Why is that gap still so wide? And how much of that is genuinely a legacy systems problem rather than, say, a strategy one?

It's a little bit of both.

And I'm not speaking personally, but I have a pretty broad network of CFOs and CIOs that I speak to and was brought up earlier.

But you can't release agents into your environment until you feel good about the integrity of data.

If you release agents into a pool of data that's inaccurate or disparate or is reflected differently in various different systems, that agent's going to return several different answers that don't match.

So part of it is legacy systems.

You have to be in an environment that you know your data is a single source of truth, you know that it's accurate, and then you can release an agent into it.