Survey: Source Control for the IT Professional [Results in]

Edit: The results are in.

I was watching Don and Jeffrey's PowerShell Unplugged session from Ignite the other day, and something stood out.

At 30 minutes in, Don asked the crowd whether they were using source control. Based on the video, the crowd wasn't big on source control.

I work in IT. If I asked that same question at work, I would likely get a similar response. Why is that? Source control is incredibly important and can drive a number of other processes, yet it seems to be an afterthought for many IT professionals.

I drafted up a quick, informal survey on source control for IT professionals. If you have a moment, would love to see your responses. Stay tuned for a rough analysis and write-up on the results [Edit: Results are in].

Cheers!

About the Author

Warren Frame

Profile photo of Warren Frame

Systems Engineer with a penchant for PowerShell, science, cooking, information security, family, cookies, and the Oxford comma.

2 Comments

  1. The problem is, you cant put mouse clicks in source control. Until more IT professionals learn to script, source control does little for them.

    I have use source control for years but them I've always written scripts and command line programs to do OPS work.

  2. Hi David!

    Agreed, I would imagine source control would grow at a similar rate to scripting, infrastructure-as-code, and other use cases.

    That being said, there are so many use cases for it outside of the PowerShell / scripting / automation world...

    Let's pretend you're a customer of Epic, or any other software vendor that really likes config files - doesn't matter if you script or not, having those config files checked into a version control system, and being able to see when changes are made, what changes were made, who made them, etc. would be quite beneficial.

    Same deal with group policies (@IT_Matt discussed a cool system he has for keeping GPOs in source control), documentation, and any other files that would be helpful to track.

    But, I suppose it adds more (perceived) work, and folks sometimes forget the work and impact to services that can happen when they don't use version control.

    Cheers!