(This post was originally published at Baggerspion) Early in my Habitat journey I packed a super-simple Python application that I had developed. It served no purpose other than to be packaged. Once I started to get my head around the fundamentals of packaging with Habitat, my mind turned to more useful things.

As you may have read about in the news, an exploit called “WannaCry” has been circulating and infecting Windows systems across the globe. The “WannaCry” exploit is a particularly nasty type of exploit called “ransomware”; once installed, the malware encrypts your files and holds them hostage until you pay hundreds of dollars in ransom fees.

To help you make the most of your time at ChefConf (May 22 – 24 in Austin) we’ve curated a list of some of our most prolific Tweeters in the Chef community. We’ll be sharing live updates from @Chef and hope you’ll join in the #ChefConf conversation.

Every year in early May, hundreds of the DevOps faithful gather in the Live Music Capital of the World for DevOps Days Austin, the world’s largest DevOpsDays conference. On this cool spring morning at the University of Texas, students clad in Star Wars t-shirts hurry to class.

It’s very common these days to leave part, or even your whole farm, on an air gapped environment. It will definitely make it harder for malicious visitors to gain unauthorized access, but you’ll have some other things to worry about regarding the management of that infrastructure.

Today, we are pleased to announce the first release of Chef Integration for Visual Studio Team Services, released to the Visual Studio Marketplace.

I’m delighted to announce that Rocket.Chat is now part of the Chef Partner Cookbook Program. They have certified the Rocket.Chat Cookbook. Rocket.Chat Cookbook The Rocket.Chat Cookbook is designed as a one-stop shop to get Rocket.Chat up and running. Run the main recipe, run chef-client, and boom, you have the base install ready to go.

We are living in a world of constant change: companies of all sizes and in all industries are tasked with being a disruptor or being disrupted. Slow-moving enterprises which rely only on legacy technology are falling behind their competitors.

This is a guest post by Michael Hüttermann. Michael is an expert in Continuous Delivery, DevOps and SCM/ALM. More information about him at http://huettermann.net, or follow him on Twitter: @huettermann.