Mmastodon BusinessBanking first seen 10 h ago, last 58 min ago, peak #7
Hardcoded UTC conversion breaks banking settlement twice a year
Original: Reconciliation broke twice a year for months before we found the pattern. Our settlement cutoff was defined as 23:00 loc
A banking engineer describes a settlement system that failed for months twice a year before anyone spotted the pattern: the 23:00 local-time settlement cutoff had been converted to UTC at deploy time and hardcoded, so each daylight saving change silently shifted the cutoff by an hour and broke reconciliation. The story has struck a chord with developers who recognise time zone and DST bugs as a classic source of hidden production failures.
Why now: Daylight saving clock changes are a widely relatable cause of subtle software bugs, and the anecdote is being shared as a cautionary engineering lesson.
banking settlement systemsdaylight saving timeUTC
Rank over time, top of the chart is #1. 8 snapshots from 10 h ago to 58 min ago.
Evidence
- Reconciliation broke twice a year for months before we found the pattern. Our settlement cutoff was defined as 23:00 local time, converted to UTC at deploy time and hardcoded. Worked fine for six months, then the clocks changed and the cutoff silently shifted by an hour… · hackaday@www.urbanmind.net · 2
API: https://socialmediatrends-api.osmike.com/v1/trends/427528