[onion2k]

A lot of the time it's not really a matter of how well or badly the code has been written. It's more that an app hasn't been deployed in a long time and the infrastructure has changed, so now you have to update the deploy process. Or that the people who worked on it have moved on and now there's no understanding of the functionality, or documentation, so running a QA check is hard. Or that the test suite has broken so you need to fix that first. Or even that you don't know which systems rely on dates so you have to audit everything.

Code quality doesn't help if things are coded in inflexible ways, but there is so much more to ops in a big company.

[jeroenhd]

If that's the case then let this be a wake-up call because there will be a time when you need to update your application in less than a week (see log4j for an example).

On 2022-08-15, IANA released their third zoneinfo database of 2022. On 2022-03-15, the IANA timezone database changed for the state of Palestine as they decided to move from DST a day later after going to DST a day earlier in 2021-10-29, which was also announced just over a week before the change.

If this is the third time this year your company has been in panic mode because of sudden timezone changes, you should really be changing your processes. Timezone databases change multiple times a year!