I think of the word DevOps, and I think of it almost like Cloud, a term that is used to describe a concept but everyone probably has a different implementation or way they go about things when it comes to DevOps. Gone are the days when engineers were going to an RDP session, and building out servers, looking at their notes to configure applications, and creating so many holes for human error. Beyond that, a process was usually in some senior engineer's head who has worked on that particular application for years within an organization. Losing an engineer could create a huge set back for an enterprise project if it wasn't documented extensively, and easy to read.
Now DevOps enters the scene, no longer do engineers have to review their notes, have a slew of OneNote notes, paper notes, and everything else on how to configure a large multi-tiered application. Settings roles, environments, and scripts to drive it all (and essentially documenting the environment in the process). Now some may be hesitant to embrace automation, but it really frees you up to focus on new things rather than spending days to build out, deploy, and maintain environments.
My life has been busy over the past year working on Sitecore and focusing on using DevOps methods to build out environments, and deployments. Not just doing an implementation, but automating the environment builds using PowerShell Desired State Configuration (DSC). Infrastructure as code is truly a reality with technologies like Chef, Puppet, and DSC. Being a Microsoft engineer I prefer DSC, but it does lack some orchestration features that tools like Chef has, but that's coming soon with PowerShell 5 and Windows Server 2016.
I'm having a lot of fun and really looking forward to PowerShell 5, my opinion is why implement a Chef architecture or Puppet, if you can accomplish 98% of the same thing using DSC. So what if you don't have the pretty web interface, we're all going command line anyway with containers, core, and scripting anyway.