• 0 Posts
  • 20 Comments
Joined 4 months ago
cake
Cake day: December 14th, 2024

help-circle














  • By “interface” I meant the data interface between systems. Not a User Interface.

    Additionally, it’s been my experience that I rarely get to design the full stack - we inevitably have to handled data exchange and legacy systems. Those legacy systems are a type of “user” in this instance that we have to program for. We can take a 13:30 string, and store it in UTC, but without location or time zone being provided through that (which the message queue that we pull from doesn’t have), it doesn’t do us anything.

    The solution for these type of problems usually involve find another source of data and mapping the time that way. This inevitably ends up being far more work for us because of the security, traceability, auditing, etc.


  • It’s like you didn’t think I had real life scenarios that didn’t fit into this fix.

    What happens when the interfaced system provides a date without timezone information? What happens when they provide multiple timezones? What happens when they have more than one site location, and they just send you a 12-hour time and date?

    You can always point to the customer - say “hey, we need better data.” But what happens when you have 4000 customers scattered all over the world?

    Or another scenario - you are doing optical character recognition, and the document always has a date/time on it. The date and time is usually printed, but sometimes it’s handwritten. Maybe part of the process is to verify that date matches with a date in a legacy system. The date in the legacy system is local to your business, but there is no information on what the datetime on the document is.

    I’ve run into so many problems with time in my career that I’m fairly certain it’s created more work than any other problem.