Architects and mechanical engineers not only know about blueprints and design procedure, they also have a solid understanding of the physics that make their des

Architects and mechanical engineers not only know about blueprints and design procedure, they also have a solid understanding of the physics that make their designs work. Programmers, by and large, just know how to code. There exists a formidable body of study describing the practices and theory required to write knowably-correct software, but the software engineering industry treats these ideas with utter derision. Even lighter-weight methods for knowably preventing broad classes of errors(e.g. Haskell-like type systems) are considered niche and pretentious. These opinions are mirrored by many CS programs, so most engineers wouldn’t have the slightest clue how to apply these methods, or even know that they exist, should they decide they were necessary. With that kind of culture, what can we expect?