My name is William Holroyd and I build massively scalable services and distributed applications for a living in Raleigh, North Carolina. I’m a software architect by title, a software developer at heart, and love anything related to technology and science.

I’ve historically been a very quiet person when it comes to social media and blogging, and have a personal goal to share my current and past experiences for others to learn about. As a result, I hope to utilize this blog much more in the near future with a collection of thoughts and opinions regarding things I’ve encountered in my professional career recently or in the past, or articles about things I’ve stumbled across worth sharing. For the content found here going forward, be warned that it may be a little rough around the edges as I’ll probably know what I was talking about, but you are requested to me know where I have something wrong and I will correct it.

One challenge I’ve encountered with the blog has been trying to produce content for others to read as I become a perfectionist when publishing publicly. As a result, I end up seeing the blog as a chore rather than a resource. As others have done before, like my friend Justin Saraceno suggested, I should try to see this place as a reminder to myself of how to do something. Rather than storing all of my resources in OneNote, make it publicly available for others to learn and for myself to relearn. Or in the case of non-technical content, a way to reflect on past thoughts and how I’ve changed over time. People change, and so do our thoughts. I personally see nothing wrong with changing your previous stances if you learned something, gained a new point of view, found conflicting views to hold a better position or level of correctness, or challenged myself on a view which found it to be less effective than originally believed. So why can’t a blog inherit that same type of self-improvement? It helps a lot to get past that blank screen, or fear of pushing ‘Publish’.

I lean heavily towards the Microsoft ecosystem given my background of working there for several years in Xbox LIVE, but have been slowly transforming myself into a polyglot programmer when I find time. I’ve had extensive experience in C# and PHP, and more recent experience in Erlang, Python, Ruby, and Node.js (current favorite). I’ll try to spread the love evenly.

In the event that I get bored with computers, you may find me dusting off my Nikon gear with landscape and nature photography.

Disclaimer of opinions

It should go without saying, but probably should still be repeated: the opinions expressed herein are not necessarily those of my current employer, my former employer(s), not necessarily mine, and probably not necessary.

Disclaimer of links

This blog utilizes Amazon links which are actually marked with an affiliate identifier. The use of this identifier allows the website to partially recover the costs of operating the blog. The prices shown in these links are no different than if you went directly to the Amazon site yourself, and only provides a ‘finder’s fee’ for driving web traffic to them (vs. Barnes & Noble, etc). Given the payout scale from Amazon, people would have to purchase about 11 books priced around $30 to offset a single month of running the blog.

At this time, only Amazon and Namecheap links on this site should be expected to utilize affiliate identifiers and all other links should be direct.