Fun, fast pasted overview of some infamous software bugs, going into details as to the logic that caused the error when possible.
SPOILER for the video's ending joke:
"There are two ways to write error-free programs; only the third one works."
--Alan J. Perlis
That reminds me of how there is a divide on how much emphasis should be put on units-in-isolation testing vs holistic, parts-communicating-in-their-contexts. Both are needed. The former is usually cheaper to put into automated systems, but the "test all hundred trees and have confidence that the forest is sound" alone idea misses the concept of emergent properties of interconnected systems...
No comments:
Post a Comment