Graham Downs on Nostr: nprofile1q…9lwq7 I think we need to make the distinction between "crying wolf" for ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq75ktej6ym7athxl7kwxvafnm58azwseptj0tad5r46m5z5d5q9mq09lwq7 (nprofile…lwq7) I think we need to make the distinction between "crying wolf" for the sole purpose of causing panic or drawing attention to yourself -- which is what the boy in the story actually did, and which *is*, in my opinion, always bad -- and raising an alarm because you genuinely think it's necessary, but then it turns out that you were wrong and everything's okay. That's not a bad thing, because it comes from a good place, and honestly, I'd rather you raised that alarm a million times and it was a false one.
The problem is, it's very difficult for outsiders to tell the difference.
It reminds me of High School: for just about my entire five years there, we had a bomb scare, on average, every single month. Sixty bomb scares, during my High School career. And each time, the entire school had to trudge out to the very far edge of our sport field and sit around doing absolutely nothing for, like, 4 hours, while the cops came with their sniffer dogs and went through each classroom and office and looked inside each kid's suitcase.
Guess how many bombs they found? None. Not a one.
Obviously, they have to take each threat seriously because if there *had* been a bomb, just once, and nobody had heeded the warning, it would've been catastrophic. But by the end of it, nobody seriously believed any of the bomb threats anymore; we just rolled our eyes with a "Here we go again", and sauntered down to the field, calm as you like. Super frustrating. But there's always the chance that that ONE time....
Yeah, I agree with you about Y2K. Many developers made a lot of money over Y2K, and while it wasn't as bad as everyone made it out to be because by the time we started working on it, most systems were using 4-digit years anyway, it could've been worse than it was if it wasn't for our efforts. Maybe people overestimated the severity of it, but it was definitely a real disaster which was mostly averted because people did actual *work* to avert it. :)
The problem is, it's very difficult for outsiders to tell the difference.
It reminds me of High School: for just about my entire five years there, we had a bomb scare, on average, every single month. Sixty bomb scares, during my High School career. And each time, the entire school had to trudge out to the very far edge of our sport field and sit around doing absolutely nothing for, like, 4 hours, while the cops came with their sniffer dogs and went through each classroom and office and looked inside each kid's suitcase.
Guess how many bombs they found? None. Not a one.
Obviously, they have to take each threat seriously because if there *had* been a bomb, just once, and nobody had heeded the warning, it would've been catastrophic. But by the end of it, nobody seriously believed any of the bomb threats anymore; we just rolled our eyes with a "Here we go again", and sauntered down to the field, calm as you like. Super frustrating. But there's always the chance that that ONE time....
Yeah, I agree with you about Y2K. Many developers made a lot of money over Y2K, and while it wasn't as bad as everyone made it out to be because by the time we started working on it, most systems were using 4-digit years anyway, it could've been worse than it was if it wasn't for our efforts. Maybe people overestimated the severity of it, but it was definitely a real disaster which was mostly averted because people did actual *work* to avert it. :)