I think that the "glory," the absence of which we bemoan in this thread, is best understood as a metaphor for the era when success in IT and its predecessor fields was mainly about being smart. If you were in what was called the data processing business in 1960, intellect was, by and large, what made you successful. That situation persisted until the mid-1980s or so (depending on where you worked), and it gradually became more important to have knowledge than intellect, and the non-technical skills (writing, teamwork, getting along with your boss, dealing with politics) became more important, too. The change was because of the drastic increases in complexity of the systems we worked with, and because the tools were so much more reliable.
In 1980, it was not an unreasonable objective to read every word of every document printed, and every line of source code, for Bell Labs UNIX. Something that could easily be done in a few months. It's not a reasonable goal, anymore, for any of the major desktop releases, and so you have to specialize, and rely on having things just work. And by and large, they do, and even people who don't specialize in technology can use computers and write Excel macros these days. They for the most part do quite well unassisted, and so the panache that came with restoring the boss's spreadsheet from a floppy disk with a bad sector isn't there anymore.
There are still good gigs out there, but they can be hard to find, and you have to make your tradeoffs among technical challenge, funding continuity, salary, management quality, coworker quality, and the extent to which the technology is strategic from a career perspective. And once in a while you still get to work around a compiler bug.
... or aircraft control and navigation, or banking, or encryption, or much of anything besides consumer products where it's OK to fail once in a while. Different situations require different approaches.
I agree, but even in those cases complexity doesn't mean better or more reliable performance. Reliability and predictability is often easier to ensure in a simple solution where there are fewer potential failure modes. Better is truly the enemy of good enough in many cases.
Yes, but you probably don't want to skip the unit test, and having a carefully thought-out design might not be a bad idea.
Spolski is smart and I usually like what he writes, but it's important to remember that he spent his formative years at Microsoft.
But if it were more commonplace, they would lose interest. Border patrol operate like cops setting up speed traps. They don't care how many smart people slip through, they care about finding the technique that nets them the largest number of arrests. If it becomes pointless, they'll change it at a policy level.
Nonetheless, this is promising work. A modern violin by the best makers is typically a $25,000 instrument, while professional players in major orchestras are expected to spend several times that for an older instrument. It's like having an extra house payment. If the quality of the modern instruments starts to rival and surpass those of lesser makers in antiquity, it will help young players immensely as well as giving speculators in such instruments a well-deserved comeuppance.
There actually are pleasant, smart, capable people out there in tech jobs and tech management.
Back then, we didn't have Windows. Now we do, and we can use Windows and Windows technologies to control our systems. Stuff like OPC (OLE for Process Control, yes, that OLE...).
And plant management can open up a nifty Excel worksheet, pulling out the numbers from the plant immediately...
</joke>
Analog control loops and things like PDP-8s weren't necessarily a whole lot more reliable than Windows. I don't know what the plant actually had for controls, but if you wanted a digital computer, the PDP-8 was fairly typical of the era. An analog meter with a d'Arsonval movement and optical sensors for the trip points was just tickety-boo in those days. Sometimes even the good ones stick.
A close reading of the accident narrative at TMI doesn't support the idea that the failure was "solved correctly." It shows that despite a grave combination of equipment failures, human factors problems, and bad judgment, the plant was eventually shut down without any leakage of radioactive material into the environment, due to a combination of conservative design and a little luck.
The main technical differences between TMI and Chernobyl were that a) Chernobyl had an intrinsically less safe graphite moderator while TMI had heavy water and b) TMI had better containment.
Anyone can make an omelet with eggs. The trick is to make one with none.