I wanted to start a series of blog posts on how to use Source Control for IT needs
What do I mean?
Source Control is considered to be a tool mainly used by development teams, and rightfully so. It is targeted towards dev needs, integrates with multiple languages and provides many tools to… well… develop.
What does an IT guy have to do with this? Usually you will get involved in Setting up Source Control, not actually using it as a customer. You will setup the server, permissions, backup, monitor, etc.
This is not what I’m here to talk about
With the evolution of IT and the IT Admins taking the DevOps route, more integration is needed from the standard IT guy towards the code area.
You may have heard terms like “Infrastructure as Code”, “Continuous Integration”, “Continuous Delivery”. They are all part of the DevOps movement.
For myself, the first step in this direction is to start developing a “developer mindset” for my self. Using the tools that developers use helps me understand what and how I can do in that world
So, this series of blog posts will talk about some of the tools I used to start managing code for my needs –
- Powershell scripts and projects
- Visual Studio Community Client
- Visual Studio Code
- Git repository
- Visual Studio Team Services
- Source Control
- Azure Resource Manager and deployment templates
If any of the above rings a bell and sounds like something you may have heard of, but… ha… didn’t quite get what is it used for or how you can benefit from using it, stay tuned