One year ago I decided to quit my consulting job at a respectable company and go rogue as the Founder and sole employee of Ned in the Cloud LLC. I thought that now might be a good time to reflect on how I feel about that decision a year in, how things are going personally and financially, and where I see the company going in the future. Come with me friend on this introspective journey to examine the real-world of an independent content producer.
Although I don’t generally subscribe to New Year’s resolutions, I do like to review my professional goals on a regular basis and make sure they align with my overall strategy and vision for my career. I suppose that the beginning of a new year is a useful reminder to check in and see how things are going. In a previous post, I took a look at my goals for 2019 and how I did on achieving those goals. I also mentioned how I needed to revise those goals for 2020 based on my new circumstances, i.e. being self-employed.
Before I can even formulate new goals for the year, I think I need to spend a little time figuring out what the long term vision is for Ned in the Cloud LLC. The vision creates a strategy, the strategy determines goals. The fundamental question is, what is the vision for me?
Three months ago I decided to leave the world of VAR consulting and try my hand at a new venture. That new venture is Ned in the Cloud LLC. I wrote a long post about the events that led up to my decision and I encourage you to go check that out if you have questions. The focus of Ned in the Cloud is to create technical content that is educational in nature. That could be courses on Pluralsight, sponsored blog posts about vendor technology, webinars about a technical topic, podcasts about the cloud, or even a book about the Azure Kubernetes Service. The unifying thread is a desire to learn about technology and share that knowledge with others. Now that I have been doing this for a full quarter, I thought it might be nice to post an update about how things are going so far.
Anyone who’s worked with Azure for a bit has encountered the need to create a service principal. If you are an IT Ops person, you probably equate an SP with a service account in local Active Directory. If you’re more of an application developer, then you may have created an SP as part of your application in Azure, because you want to give that application permissions to Azure resources. The purpose of this post is to tease apart what service principals are, how they interact with application objects, and all the myriad ways to create an SP on Azure.