Editing 1883: Supervillain Plan

In computer programming, working with dates and times can be complicated. Think about {{w|Leap year|leap years}} or {{w|Leap second|leap seconds}}, the non existing {{w|Year zero|year zero}} which even worse for scientists does exist in {{w|Astronomical year numbering|astronomical calendars}}, or the {{w|Year 2000 problem|Y2K}} and {{w|Year 2038 problem|year 2038}} problem. Nevertheless in this comic there is only a ''time zone problem'' mentioned. To handle this the {{w|tz database}}, also known as ''tzdata'', provides all relevant information for every country back to 1970 and, less accurate, before. But it's still up to the programmer to use this data in useful ways.

In computer programming, working with dates and times can be complicated. Think about {{w|Leap year|leap years}} or {{w|Leap second|leap seconds}}, the non existing {{w|Year zero|year zero}} which even worse for scientists does exist in {{w|Astronomical year numbering|astronomical calendars}}, or the {{w|Year 2000 problem|Y2K}} and {{w|Year 2038 problem|year 2038}} problem. Nevertheless in this comic there is only a ''time zone problem'' mentioned. To handle this the {{w|tz database}}, also known as ''tzdata'', provides all relevant information for every country back to 1970 and, less accurate, before. But it's still up to the programmer to use this data in useful ways.

Time zones and DST can give seemingly nonsensical results when used improperly. For example, a flight going west might leave at 02:00pm and reach its destination at 03:00pm while the reverse flight will leave at 02:00pm and arrive at 05:00pm. In both cases, the travel time is two hours, but the one hour difference between the two time zones makes it seem otherwise. You might even find yourself arriving at your destination at an earlier time than your departure! DST can also makes a given time mean two different things, if after 01:59am you go back to 01:00 am, 01:30am can either be one hour after 00:30am, or one hour before 02:30am. Or in the reverse change, some dates don't actually exist, like 02:30 when going straight from 01:59 to 03:00. Humans often avoid this issue by being in only one place at the same time{{Citation needed}}, or by sleeping when the DST changes happen, but computer communications often span over large distances, and drones don't need to sleep at night. Megan wants to make sure she won't have to deal with the difficult problem of communication between drones and other systems with those issues, where a single poorly communicated date can have disastrous effects (although possibly far less disastrous than moving California into the sea{{Citation needed}}).

Time zones and DST can give seemingly nonsensical results when used improperly. For example, a flight going west might leave at 02:00pm and reach its destination at 03:00pm while the reverse flight will leave at 02:00pm and arrive at 05:00pm. In both cases, the travel time is two hours, but the one hour difference between the two time zones makes it seem otherwise. You might even find yourself arriving at your destination at an earlier time than your departure! DST can also makes a given time mean two different things, if after 01:59am you go back to 01:00 am, 01:30am can either be one hour after 00:30am, or one hour before 02:30am. Or in the reverse change, some dates don't actually exist, like 02:30 when going straight from 01:59 to 03:00. Humans often avoid this issue by being in only one place at the same time{{Citation needed}}, or by sleeping when the DST changes happen, but computer communications often span over large distances, and drones don't need to sleep at night. Megan wants to make sure she won't have to deal with the difficult problem of communication between drones and other systems with those issues, where a single poorly communicated date can have disastrous effects (although possibly far less disastrous than moving California into the sea{{Citation needed}}).