I got my start in IT doing solely operations stuff: swapping out bad hard drives, terminating my own CAT5 cables, (I still carry a TIA-568 wiring diagram in my wallet in case I forget... had to throw out the condom to make room for it though, because let's be honest - I'll be using one way more than the other, just kidding, btw,) administering Active Directory, doing file server migrations... things like that. And I still do mostly operations stuff today. But I've also been playing around with programming since I was 14 years old, and I still do, even though my current job doesn't usually call for it. Most of the time coding is just a hobby for me, but when there's a specific problem at work that I think I can solve with a little of my own programming elbow-grease, I'm all over it. So I guess that makes me a natural participant in the DevOps movement, which is interesting because the age-old friction between IT pros and developers is still present. On one hand, I get the idea of "don't half-ass two things; whole-ass one thing." I think something that will ease that tension between Dev and Ops is the realization that developers aren't just developing boxed products anymore, but services. Everything's a perpetual service now. Which means the code and the hardware running that code have to evolve together now, at the same time and with the same goal. (Case in point: The OpenCompute Project, wherein we see entire datacenters being designed around the idea of running these super-scalable cloud workloads.)
Which means the developers and the IT pros need to hold hands and sing Kumbaya.
So Microsoft has been announcing tons of interesting things the past few weeks, such as Powershell 5 with OneGet, the open-sourcing of Roslyn the C# compiler, the introduction of .NET Native, etc. And that got me into a bit of a mood for software the past few days. Something I was way behind on was Git and GitHub. Didn't know what they were, how they worked, how to integrate it into Visual Studio, etc. So I've taken the past couple of days to educate myself, and the result is that now I have a public GitHub account. I've only uploaded a few of my old personal projects - I will likely upload way more in the future. I also have a ton of Powershell stuff built up, that I'll probably just make a single repository for.
Don't be too hard on me if you're going to scrutinize my code. I'm self-taught and I feel like I'm pretty terrible... but maybe I'm my own biggest critic. I'm like the fat guy at the gym with all the other people with amazing bodies thinking to themselves "well at least he's trying..."
Git was originally designed by Linus Torvalds as a distributed source code revision tool. GitHub is a place where you can store your repositories, and public code repositories are free! You use Git to upload source code to GitHub. Git/Github have established themselves as the premier service of its kind, which is evidenced by the fact that Visual Studio now integrates seamlessly with it and you can push commits to your branches (<- see me speaking the lingo there?) directly from within VS on your desktop.