### Forced Boredom

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.

Development and elaboration on ideas presented in the three info-ops books

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

One-hundred years ago a logician pointed out that naming variables is hard. Programmers can (and must) fix this problem

"It Is Difficult to Get a Man to Understand Something When His Salary Depends Upon His Not Understanding It"

Ok kids, we're going to refactor all of the modern education system. Who wants to go first?

Chaos, Cynefin, Complexity, Hexagonal Architecture, and Onions