How much effort was spent automating this to fix 112 instances across Uber’s code base? I assume code reviews would catch any new issues so this seems like overkill for a small one-off task?

Epic is used extensively in the UK, Europe and Australia so to say it’s a regional thing seems odd? They’re speculated to be one of the largest privately held companies in the world.

There’s a whole concept of records management in enterprises that manages the disposal of data. It’s far more complex than just purge dates as there’s often regulatory requirements and legal discovery issues so <2% of data is actually disposed due to perceived risk.

For personal data, the concept would be simpler but still has requirements like say tax records need to be kept 7 years.

They didn’t want to make a breaking change but didn’t:

1. Use UUIDv7, which has the same sortability without breaking the ID format, or

2. Repackage the ULIDs to maintain consistency

And then broke pagination with this change?

How was this ever approved by a change control board? Or do they not have one?

From just reading the README, the example is not valid JSON. Is that intentional?

Otherwise it seems like a prompt building tool, or am I missing something here?