Ask HN: Did you encounter any leap year bugs today?

Article summary

A company's billing team encountered a bug that charged monthly subscribers for an extra day due to the leap year. The issue was resolved after a frantic scramble, and a postmortem is scheduled for 2028. The bug was related to the company's test suites and SRE. The team had to patch the bug to ensure accurate billing for their subscribers.

Main themes

• Leap year bugs
• Date and time calculations
• Software testing
• Billing and subscription systems
• Timezone and calendar issues

What commenters say

• The concept of subtracting a year from a date is ambiguous and can be interpreted in different ways, leading to potential bugs and errors.
• Using a fixed number of days to subtract a year can lead to inaccuracies and does not account for leap years or other calendar irregularities.
• Some argue that programming languages should provide a clean and unambiguous way to subtract a year from a date, while others believe that the ambiguity is inherent to the concept of a year.
• The use of libraries and frameworks, such as dateutil or Arrow, can help mitigate issues related to date and time calculations, but may not entirely eliminate the problem.
• The discussion highlights the importance of careful consideration and testing of date and time-related code to avoid potential bugs and errors.
• Some commenters suggest that the concept of a year is not as straightforward as it seems, and that different cultures and calendars may have different definitions of a year.
• The leap year bug experienced by the company is not an isolated incident, and others have also encountered similar issues with their systems and code.
• There is no one-size-fits-all solution to the problem of subtracting a year from a date, and different approaches may be necessary depending on the specific use case and requirements.