Editing 1985: Meteorologist
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 38: | Line 38: | ||
===Questions from the software developer meteorologist=== | ===Questions from the software developer meteorologist=== | ||
− | In the title text, the news station has made the same error | + | In the title text, the news station has made the same error again, this time by hiring a software developer as the third meteorologist. This last person is stating concerns about the feasibility of the time system used to correlate to the weather patterns. Because it appears simple, many people would simply assume they understand what is being said when a meteorologist talks about "12pm" or "1pm". This is a common mistake because [https://www.nist.gov/pml/time-and-frequency-division/times-day-faqs#noon noon is neither post meridiem (pm) nor ante meridiem], and should be stated as "noon" or "12 noon" instead of "12 pm.". However, because software developers frequently have to deal with things such as specifying exactly what time-label means what, the new meteorologist begins to wonder what time period is actually meant on a per-hour forecast. On such an hour forecast does 12pm refer to the hour from 12 to 1pm, from 11:30 to 12:30 or is it actually only to the weather precisely at 12:00 that is referred to? The software developer also worries about an {{w|off-by-one error}}, which is a common error in software development occurring when boundary conditions include one element too few or too many: when counting by 24 once every set period (for example), it is common to forget whether the count should stop at 23 or at 24, especially if the number 0 (midnight) is included. In the 24-hour forecast, that means there's 25 hours represented every day, and the software developer worries that these 25 hours might add up and, every progressive day, the forecast is one more hour off. (If the news station's meteorology department had been around for a while, worrying about this would be absurd because if the new station tried to predict the weather one hour further into the future each day, it would eventually ask for the weather further into the future than the forecast models could supply, resulting in an error that someone would definitely notice (and it would likely be the case that long before that happened, someone would perceive the weather forecasts as being inaccurate or early). However, based on how quickly the linguist was fired, this was likely either the mathematician's first day or second day on the job, so if we assume that the mathematician was the first meteorologist (or that all previous meteorologists were fired quickly enough that the mathematician started within a few days of when the meteorology department started), there wouldn't have been enough time for the effects of an off-by-one error to stack up enough to be noticed, so the software developer's concern about an off-by-one error would not have been ruled out yet.) In theory these are valid concerns and notably less inane than his predecessors, but they are all things he should have asked ''before'' he went on the air. |
− | |||
− | The software developer also worries about an {{w|off-by-one error}}, which is a common error in software development | ||
− | |||
− | |||
===Answering the meteorologists’ questions=== | ===Answering the meteorologists’ questions=== |