The Chef Win Series is a response to: "How has Chef changed our operations for the better, in the past 2 years since our shop adopted it?"    Example:

Testing, Made Real

Two years ago I was trying to explain to my partner - an ops guy - why devs love automated testing. "You see, I often develop one thing, only to break something else without realizing it. This is my life as a dev. So I use automated regression testing as a safety net."

Like most things that devs say, my partner did not even pretend to listen. But he was implementing many new Chef recipes, and as he built them - especially with multiple recipes on the same box - he began experiencing some of this same need to automate regression tests. Read more »

The Chef Win Series is a response to: "How has Chef changed our operations for the better, in the past 2 years since our shop adopted it?"  Example:

If you've been in IT very long, you've been burned by binaries changing underneath you as you are working. It could be in a Ruby update, or "DLL Hell" as we used to call it in the old client-server days. Or it could be jar hell in java, where a new binary slips in, and a JVM changes behaviors underfoot.

When an underlying binary changes and breaks your app, you have no idea which of the dozens of binaries it is, or how to restore it to a working version. In many respects, you're simply effed. Read more »

The Chef Win Series is a response to: "How has Chef changed our operations for the better, in the past 2 years since our shop adopted it?"
An additional perspective:

Challenges - the Background

I challenged Chef not even a year ago to acknowledge and solve these problems. Read more »

The screencast below brings up many different approaches of modularity systems in Java. Hmmm. I never even considered anything beyond OSGi.

  • OSGi
  • JSR 277
  • JSR 294
  • NetBeans Modules
  • Maven
  • SMS
  • Jigsaw

Jaroslave Tulach, the guy who wrote the netbeans module system is interviewed here, it's a great discussion.