3 ms·

My opinion is that technology development is going to have to bifurcate -- or perhaps even split into three paths. No longer can you simply sit down and code so

My opinion is that technology development is going to have to bifurcate -- or perhaps even split into three paths. No longer can you simply sit down and code something. Instead, you'll need to code some set of "rules" (this system can't use the internet, it should never access the GPS, and so on) at the same time. Technology will "run" when all the separate systems agree that everything is behaving correctly. We've tried to do this with various XML/manifest declarative constructs, but the problem is that these constructs just rely on subsystems which are themselves insecure. These systems will have to be baked into the metal, and they're going to need to come from different vendors. Unlikely to happen, but that looks like the way forward.

InclinedPlane 12y ago
Well, yes. A big part of the problem is the lack of terminology and models. "Software development" is a stupidly large scope, it encompasses activities that are comparatively as varied as backyard astronomy and heart surgery. There are many different kinds of developers and many different kinds of software, but we lack the words to express the differences clearly. Which makes it that much more difficult to improve processes and standards. It's common for bromides and recommendations to be made as blanket statements applying to all software development, when it's clear that no one set of practices could possibly apply universally. Worse, many devs aren't even aware this is a problem, and few people are working on fixing it. We're deep in a morass that will take a long, long time to get out of.