sleet_spotter
Joined 3 years ago
Joined 3 years ago
The other dimension implied here is the timing of when variety is introduced. If all the options were known when the system was originally designed, the issue may have been more clear. So then the other problem is that, when the need to distinguish between cases first came up, the solution was designed for only 2 cases. And if there were only ever those two cases, the solution presented would probably be the most efficient.
The solution to this incremental scope problem is a lot less clear to me and something I struggle with personally in scientific computing projects. When variety #2 pops up, how does one decide whether to restructure everything in case of a variety #3, or take the quicker (potentially more efficient) path and avoid unnecessary complexity? Assuming I've done as much as I can to anticipate and constrain my needed functionality. It somehow feels like I end up losing either way.
Also, I certainly don't mean to detract from this achievement . This is great work and it is truly awesome to see these kinds of leaps. There is plenty of vanity in science and the urge for self-preservation, but such advances in weather forecasting will save so many lives and do a lot of good in the world. I wholeheartedly cheer on the scientists behind this work and am excited to see what is around the corner.