|
|
|
|
|
by harry8
2054 days ago
|
|
Which engineers to trust? The ones saying Y2K needed billions of investment or cars all crash with planes falling from the sky as we usher in the post-technology age Jan 1, 2000. Remember that? Some people still believe them that we headed it off successfully, everywhere on earth in every industry, regardless of how little was spent, including nothing at all... You can't trust engineers anymore than you can trust lawyers (which lawyers?) or Doctors (Second opinions ever much?) Or indeed scientists, managers and politicians. The question to ask is "Do you have good reason to find this convincing." When what is at stake has sufficient value proving the obvious is indeed, also correct, beyond doubt has very real benefits. |
|
We also had some pretty fair warning from industries that use long-term thinking. Banking software was already breaking in 1969 (30 year mortgage logic). For many industries this was a long emergency.
Even by a cynical view that these were pork projects that didn't 'need to get done', so what? We do these all the time. The cash infusions prop up industries or divisions, and often serve as cover for attacking deferred maintenance. Over beers you can complain about how stupid it is to have to get things done this way, but at work you take the money and run as far as you possibly can.
What bothers me most, I think, is that if you've worked in software for very long at all, you should know all of this. Politics and proxies come up if you work at a mature company, or one that matures while you're there.
(On December 31st 1999, I watched the New Year's celebrations for Tokyo and Australia. When they didn't blow up, I agreed to make plans involving alcohol for the evening. By the time Europe didn't blow up, I figured we were gonna be okay, so Happy New Year to me.)