Related: Winner’s Curse? On Pace, Progress, and Empirical Rigor
Related tweetstorm: https://twitter.com/www_ora_tion_ca/status/1028010688650911746
It was interesting reading the reactions.
For as long as I can remember, people who have observed software development (insiders as well as outsiders) have compared it unfavorably with other professions when it comes to stuff like safety, verification, and adhering to standards.
But the thread is full of “well, actually”s from people who seem to think that the current way of designing software is just fine, and it’s bad people attacking software that’s the problem.
Neat stuff. Googling it led me to this work in a slide deck:
Formal Specification and Analysis of Robust, Adaptive, Distributed Systems
Cool. Thanks for sharing!
Have you read it? Would you mind reviewing it? Who should read it and why?
I’m about halfway through right now. I’d recommend it to anyone writing software; it’s like a shorter, more concise version of “Code Complete” but with better examples and with some unconventional wisdom (such as long methods aren’t bad if they encapsulate complex logic from start to finish)
Another successful export: https://twitter.com/mikarv/status/1012386696934182912