Cian Butler

I have to just follow the API contract.

I would love to say that we as an industry should be following the standards, being so strict to them.

And I can totally see that if I look back at me five years ago, I would be there shouting, no, no, follow the standards.

We should make everyone who doesn't follow the standards feel the pain.

The issue is there, that's a lot of people.

That's a lot of pain and it's not something you can fix overnight.

Like we, I know because I work in a package company, a lot of people run a lot of different versions of the same software.

So even if like we started making tools stricter, every, everyone on December, on February 28th decided to do one launch where everything switched to strict mode, they

the in every library we don't have to get that rolled out to every version of that software it's not going to be it's going to be a painful rollout

you need to have a level of permissiveness in the clients.

But saying that, I don't want a default to be permissive.

The default should be perfect.

It should be the best way a client should run.

The client should have timeouts.

It should have sane defaults and should follow the standard.

But when you run a legacy system, you're going to have a lot of weird legacy issues and you need to be able to flip those switches off.

to main that you can enable these things.

Otherwise, you're going to end up with a lot of duct tape around your very strict system to flip those switches off.

The project could have gone a lot better.

Like, it's still underway.