My passion has always been tech. Growing up my neighbour’s old computers often found their way to me, and I have fond memories of building myself a 486DX2 "gaming pc."
That computer was when I leant about the capacitors in power supplies. It turns out that if you're swapping the fan in one of those for one with LEDs in it you probably shouldn't twist the wires together by hand. Who'd have known?
Next week I'm starting in my new role at Chocolatey Software, a company on my personal "drop everything to work for" list.
My "learning journey" so far got my foot in the door at Chocolatey, and on the other side of that door is a whole new set of technologies to learn and challenges to overcome.
This particular journey never ends, there's always more to learn.
The Journey So Far
Coming out of high school, it would have made sense for me to go to university and "do" computer science. At the time, New Zealand hadn't yet introduced interest free student loans at the time, so I ruled out that path into a career.
I tried enlisting in the Royal New Zealand Air Force, the plan being to become an avionics technician, but that didn't pan out.
For a while I was a kitchen hand.
Eventually I ended up at a local sawmill. That sawmill was big on training and through them I sat a number of national standards on "Solid Wood Processing" and "Wood Processing Technology" including "Demonstrate knowledge of tree growth and physical characteristics of wood" and "Handle, sort and stack timber."
It's not the path I'd expected life to take, but in hindsight I was very grateful for it. When it came time for my (now) wife and I to move those qualifications made it easy to find work in a sawmill in my new town.
But it wasn't what I was meant to be doing. Timber was earning me a living, but it wasn't tech. And tech was where my heart was.
I decided I had to pull the plug eventually. I quit my sawmill job and started a diploma in ICT at the local technical institute.
A year later, I had my diploma and I was considering rolling into another two years of study to upgrade that to a bachelor's degree. But study was losing its appeal and, in all honesty, living on part time work is hard.
It took a while, and another stint working at a sawmill, but eventually I landed my first real job in tech on the help desk at the local city council. My first day there was building my workstation (so that I could get an appreciation for what was in the deployment image) and I was loving it.
In the office was a copy of Windows PowerShell v1.0: TFM (2nd Edition). This book was the catalyst that set a fire under my career in tech. It was what taught me PowerShell and what made me realize automation was something accessible to even a junior like me.
For there I was off.
My passion for automation had been lit.
Over time I caught the eye of the infrastructure team and was poached from the helpdesk. The scope of what I could touch with my scripts expanded, and I was exposed to lots of exciting technology.
I was officially a Sysadmin.
One of the main things I discovered along the way, was the PowerShell community. I can honestly say that my passion would have probably died out years ago if not for the people I've met and friends I've made along the way.
It's a common thing to hear about MMOs, especially the likes of EVE Online: It's not going to be the gameplay (or tech) that keeps you coming back for more, it's the community. In games that might be your clan, but in tech it'll be the familiar names on Twitter or on forums.
Putting faces to names at conferences (remember those?!)
I'm going to be providing some resources later for those wanting to get into the same field as me, but even more important than that is get involved in the community.
That could take the form of:
- Follow, and use, #PowerShell on Twitter
- Get involved in the PowerShell.org forums
- Read blogs (and comment), and write your own too!
- Jump into the monthly #PSTweetChat Twitter chats (first Friday of every month from 1PM Eastern)
Always More to Learn
In tech, as in life, there is always more to learn.
I'm very glad to have made the effort, though I can no longer claim to be more qualified to handle timber than servers.
Going forward I'm personally diving deep into all things configuration management, and exploring what other languages I should pick up to bulk up my automation toolbelt.
But at the moment I'm taking a bit of a detour from that. Some of my fellow MVPs and I are having a little learning competition which has me branching out into the wider Microsoft 365 stack.
If you're interested in reading learning stories from other MVPs, check out #TheMVPChallenge.
I've been surprised at how much I didn't know on the compliance side of things. It's an important knowledge domain to be familiar with and something to be always thinking about when building your cloud solutions... even if it's knowing enough to know when you should call in a compliance expert.
Learning PowerShell Today
I mentioned that I first started learning PowerShell from one of the very original books on the language. That book was actually written, from what I understand listening to keynotes from Don Jones, with the aim of getting people familiar with VBScript up to speed on PowerShell and not really for sysadmins looking to start automating their world (that came later with the Month of Lunches book(s)).
These days there are a plethora of options available to get started learning PowerShell, Azure and more.
Specifically on the PowerShell front, I like to refer people to the resource that Chrissy LeMaire posted. It has recommended books, videos, websites, and tools to get you going.
For those wanting to put Microsoft Learn to good use (seriously, the labs are such a good idea and super helpful for getting hands on) I put together a collection to sink your teeth into. Check out The Sysadmin Collection: PowerShell, Azure, Containers.
This collection covers most of the footprint of the AZ-104 exam, the new PowerShell content, and a little introduction to Docker and Kubernetes.
Part of the MVP Challenge is issuing a challenge to someone to give my collection a go... rather than singling someone out, I'm going to challenge the entire PowerShell community. There is a noticeable lack of PowerShell content on Microsoft Learn, compared to the likes of Azure CLI and even the likes of Python. As a community we need to take and promote the new PowerShell content coming out to show that there is a market for it and that it is worth investing in.
We also need to provide feedback. There is only a small team working on this stuff and they can't necessarily cover everything nor get everything 100% correct on the first go. Feedback from the community helps improve the content and also helps steer the team towards which content to work on next.
Be vocal. Be kind. Always be learning.
Oh, and if you complete my Microsoft Learn collection... please let me know on Twitter.