6
envolt
6y

How 2018 brings an aww bug.

At my company, we've a reporting application. Which kind of provides analysis of client's weekly business. When you open the application it shows their business trend starting from Sunday to day of week.

As usual their is an endpoint to get the data basis on start date. As soon as date changed to 1st Jan, it stopped showing data. Given that it was a long weekend, no one was available from the tech. Support team got tremendous amount of tickets for this. Later on Tuesday while debugging we got to know while forming the date in the application the logic was like this

- get current year
- get the date and month on start of week

Combine these 2 and request the data. All the time it was fetching data starting from 31 Dec 2018.

😒😒😒

Comments
  • 3
    Ah :), dates, you just have to love how they manage to make things complicated ;)

    Like how the first week number can be either 1 or 53 depending on which day January 1 is.
  • 1
    What you're describing is a classical BI Dashboard for Operational Systems, based on a Data Warehouse.

    Don't reinvent the wheel, there are well established standard practices, as well as products (free and non-free) that cover these scenarios quite well. If one would follow such practices, then one would get quite a rich functionality, that, as long as the input data is consistent, is virtually free of any bugs.
Add Comment