I had the amazingly good fortune to spend nearly two weeks in Cuba with an entrepreneurship outreach program recently. As you might imagine, there was a bit of bureaucracy involved. We had to go through several layers of travel agencies and the Cuban government had to approve our detailed itinerary. They're not really known for welcoming this kind of attention on the brilliant Cuban minds working to evolve their economy. It's not exactly clear how well it fits into the Cuban model, you see.
A while back I created the http://puppetlinter.com website. It allows you to quickly and easily validate Puppet code against several different versions of Puppet. Today Josh had an idea. Why not a bookmarklet to easily validate Puppet code from a website. Why not?
- drag the bookmarklet link above to your bookmarks menu.
- Highlight some code on a webpage.
- Click your bookmarklet link.
The traditional development cycle for training courses, technical or otherwise, is a little different from the software development you may be used to. Think of all the artifacts in a typical training course. You probably get manuals to take home. There might be a few videos to watch. Instructors must be trained on the material. Labs and exercises must be designed and tested and tested again. Marketing assets must be generated and distributed. Facilities must be booked, along with any network requirements. If it sounds exhausting, that's because it is. That's why most training courses have a measured development cycle. A course is developed, proofread, tested, debugged, and then released. Put a fork in it, because it's done. Time to start again on the next course--scheduled for release in 6-8 months if you're lucky.
My Puppet Labs training is a little different. We move at a different cadence and might release three times in a week, if needed. Read on to find out why and how we manage this without losing our sanity.