In this meeting of the State Changers, the main focus was on the problem of updating and filtering data based on time zones and working hours. Key discussion points were around how to update the timestamps for different locations and how to fetch relevant data based on specific criteria, where certain places should be active or inactive based on their local time.
The team used a hypothetical tool, similar to or might be Firebase, to manipulate their data. A function stack was used to enact these processes. Initially, participants attempted to convert offset time into hours and minutes and add it to a UTC timestamp. However, they struggled with the problem of the data being stored in seconds, not milliseconds, causing initial attempts to fail. Instead of updating every single time zone and then filtering the data, the team decided on a more direct, streamlined approach. A core feature of this new strategy was saving the offset time beforehand, which allowed them to compare it with the current time and make a more intelligent query, essentially eliminating the need for the task to update all data. Overall, the conversation highlighted the importance of time zone consideration when manipulating database records, and implementing logic efficiently to solve computational problems. The focus was primarily on back-end development and database manipulation rather than specific tools like Xano, WeWeb, FlutterFlow, Zapier, and others. By the end of the discussion, the team were able to filter out the data efficiently using the newly implemented method, making this a constructive meeting with beneficial outputs in problem-solving with timestamp and offset time calculations inside the data stack.
(Source: Office Hours 9/30 )
