A Data Type Crime So Severe It Requires the FBI
Description
A four-panel comic strip from 'Safely Endangered' depicting a programming crime of epic proportions. In the first panel, a character reports to a police officer, "Officer, someone used floats to store dates." In the second panel, the unimpressed officer replies, "And you thought this was police matter". The third panel shows the officer looking at his phone, his expression shifting to shock and disgust, uttering, "Jesus Christ......". In the final panel, the officer is on the phone, escalating the issue: "Hello, FBI? We got a situation way above my pay grade." The humor lies in the extreme overreaction to a seemingly obscure technical decision. For experienced developers, using floating-point numbers to represent dates is a cardinal sin because floats have precision issues and are ill-suited for the exactness required for timestamps, leading to subtle and infuriating bugs. The meme elevates this poor coding practice to a federal crime, a relatable exaggeration for any engineer who has inherited a nightmarish legacy codebase
Comments
7Comment deleted
Using a float for a date is like performing brain surgery with a hammer. You might get the general area right, but the rounding errors will cause a slow, painful, and untraceable death for your application's logic
New incident policy: if you find a float in a timestamp column, skip git blame and dial law enforcement - it’s cheaper than replaying the entire event stream to fix the time-travel bugs
The real crime here isn't using floats for dates - it's that somewhere, in production, there's a system calculating interest rates where February 30.999999 is a valid date and nobody knows why the quarterly reports are off by 0.0000001 cents
The real crime isn't using floats for dates - it's that moment six months into production when you discover your financial transactions are off by microseconds because someone thought 'close enough' was acceptable for temporal precision. At least with proper datetime types, your audit trail doesn't require a forensics team to explain why February 30th exists in your database
Using floats for dates: where leap seconds are “rounding errors” and the audit trail becomes “UTC-ish” - the kind of bug that escalates from SRE to Legal
Using floats for time is how 1970-01-01 and payroll day become “approximately equal” - that’s not a bug, that’s a multi-agency incident
Float dates: Where leap days vanish into 28.999999999, turning every cron job into a time-travel bug hunt