Kari and I had dinner last night with some good friends who have just opened their new dojo1 in John's Landing, Portland. Along with the beer and wine, we had lots of philosophical discussions, because that's how Tony is. He's fully immersed in this philosophy and is happiest sharing this love with people he cares about. It's part of what makes him such a great teacher.
People often ask me for advice on designing or delivering training material. One of the most common questions is how you determine the appropriate pace for the training courses or the lab exercises. It's no surprise, that's a tough question. The answer is suprisingly straightforward though.
I ran into yet another explanation of the Monty Hall problem the other day that was rather difficult to follow and it struck me that even though it's a simple problem, I still have not seen an explanation that makes intuitive sense. So here's my take at it.
In case you haven't seen it before, the problem goes a bit like this. You are faced with three doors. Behind one door is a new car and behind the other two doors are goats. Choose a door.
By now in your Puppet career, you've almost certainly been exposed to the phrases declarative state or state modeling. You may even have a pretty good idea of what the words mean. But how in the dickens do they relate to configuration management? The confusion only makes sense. We've been writing shell scripts to provision, configure, and even boot our computer systems for forty years. It's going to take a mighty strong argument to change that habit now.