One is surprised such a thing is possible at all
Development and elaboration on ideas presented in the three info-ops books
Let's talk about Symbol Behavior Mapping and how you should be using it daily to become a better and happier programmer
Our profession does structured analysis in a way no other profession has ever done. Let's not lose that precious gift.
I don't know. I may never know. It may be truly impossible. That's the fun part. Even more fun is the process to solve them.
So we have two questions here: One, how do we draw boundaries around our computer programs such that we minimize the risk of any one concept failing? Two, how do we define any one term such that it is impossible for there to be a misunderstanding or for the program to crash?
My friend, your book premise is horribly whack, but good news: the details can stay the same as long as the reader understands that this is only Step One