Our goal is to help individuals and teams become DevOps Masters. 

Check out the news stories about DevOps we tweeted:

Blog Posts

DevOps Blog

6 things to think about when you are writing your communications with other teams.  We explain why it's just as important to explain why you are communicating as what you are doing.  Remember a little time spent preparing a message can save you days, weeks or months of time trying to get everyone to understand.

Automated Deployment or Automated Build tools are all complicated to give a true evaluation.  In this post we help you set yourself up to drive to the right tool for your environment.

In this post we discuss what to look for and how to choose a Code Management Tool.  Remember to check out the podcast if you don't have time to read it.

We discuss Monitoring tools and how to pick the best one for you!!

This article and show is all about how to choose a Configuration Management Tool.  

So what DevOps Tool should you deploy first?  Check out what we think!!

Seriously why do people always have to think that if we just implement X it will solve all of our problems?  It can't and won't because a tool or methodology is rarely the biggest problem.  Most buzzwords over promise and under deliver.  Here is what I think...

Part of any successful campaign to win people over to doing things in a DevOps style usually requires some sort of promise of it being a better way.  So how do you prove you are seeing benefits as you start to implement your plan?  How do you quantify all the unlogged hours you put in doing things manually after you have just automated it.  Sure you and maybe your boss will notice you have reduced your hours down to 80 hours a week, but what about the people at the top?  The ones who ultimately need convinced to let you keep spending time on it?

That's right don't even attempt to do DevOps without Change/Incident Management. Not because you won't be successful in at least small ways. Not because people won't appreciate you automating your companies one hundred and fifty servers in five minutes instead of five days. But because you won't be able to prove any benefit of DevOps to Management. That means they won't appreciate it, value it, or the most important part FUND it......

Don't start automating it until it's documented.

You really need to know what you are going to automate before you start automating.  Documenting the steps makes everything easier.

This week we discuss whether or not you should learn a framework or just the language first?  Does learning a Framework do you harm?

Where to begin and what language is a question the DevOps Master get's often.  So at a readers request he decided to give out his recommendations.  He also explains a little behind the wars between the languages.

Why does Continuous Integration(CI) matter?

What is and why should I care about Continuous Integration?  This article tries to give you a brief explanation.  Check it out and see what you have to add to the conversation.

Scriptors really are developers who just refuse to admit it.  But there are differences as subtle as they are.  Most really need to learn a few simple things from developers to make their lives easier.

If you don't know how to script you won't be able to find a job in five years.  If you think being a Windows Admin can save you think again.  This article explains why!!

DevOps is the term currently used for Systems Automation.  The art and craft of making building and deploy processes for complex systems and applications reliable, repeatable and maintainable.  But that is just the begining.  Check out this article for more details. 

Knowing the difference will help you prioritize your work in DevOps.  This really does make decision making easier.  So check it out so you know where to go with you next event.