O'Reilly Software Architecture NYC 2020: Intellectual Control
In the early days of software engineering, Edsger Dijkstra warned us not to let the size and complexity of our programs cause us to lose “intellectual control” due to the limited nature of our minds. Dijkstra never defined precisely what intellectual control was. Our software today is staggeringly larger than the programs of the 1960’s, so does that mean we have it under our intellectual control or did we find ways to make progress without Dijkstra’s high standards?
If you found this interesting, you’ll want to try these next:
- Intellectual Control
- Testing Numbs Us to Our Loss of Intellectual Control
- Code is King; Let’s Think in Code
- Continuous Design of IT Systems
This talk was a keynote at the O’Reilly Software Architecture conference NYC, 26 February 2020.
Here are the slides: