Back in December I moved my blog to Hugo running AWS, and of course I blogged about in Ch-Ch-Ch-Changes. After that move, I lost some of the visibility into my blogs operations that Azure provided. Worse, I did not have enough visbility into my blogs costs. Not that it is running that expensive, but even after tagging my resources, customizing my reports, I really didn’t have the transparency I wanted.
My blog has changed again, in two different ways. First, I have moved from Jekyll to Hugo. Second, I have moved my blog from Azure to AWS. So why the changes? Azure to AWS Let me start with why I am changing cloud providers. A couple of simple reasons. In fact, they are the most basic of reasons: cost and convenience. I have had a very hard time getting an accurate cost for Azure.
I am saying goodbye to Walmart. After years of being a customer, our time together has finally reached the end of the road. Not over some major issue, but over the very basics of customer relations. The Goal Earlier, I decided to get a Google Chromecast to use for a repeating presentation in a lobby. I am not a 100% sure it will work, but it was at the right price point to give it a try.
Ten years ago, May 14 2005 specifically, I started this blog on the WordPress platform. I chose WordPress for a number of reasons, but the primary reasons were that it was simple - really simple - for me to get up an going and that the hosting providers I was considering supported it. I wanted to use the web, but not actually develop for the web. WordPress seemed like the right choice.
I am going to diverge from my normal blog post topic of programming to talk about another passion of mine – fiction. I enjoy writing it, and more importantly – greatly enjoy reading it. One of the authors I have started to read recently is John Scalzi. His Redshirts book was the first of his I read (ok – I listened to it using Audible, but I am still calling it reading), and I was hooked.
Nope. It’s not mine. Though I wish it was. It is an older post (from the distant past of 2012) on the Highly Scalable Blog entitled NoSQL Data Modeling Techniques. This past weekend I found myself looking for methods of storing hierarchical data in a key-value store (a subject for another blog), and in the spirit of not reinventing the wheel – I broke out my trusty Google search window.
It has been a long time since I upgraded this library, and the .NET development world has shifted a bit in that time. One of the key changes is the move to Portable Class Libraries, and Caliburn.Micro is one the libraries making that change. I have decided to follow suit and make the core Caliburn.Micro.Logging library portable. This, of course, has creating some significant breaking changes, so please look over the changes list below.
Sometimes time flies way too fast. It has been seven months since I last updated my Caliburn.Micro logging frameworks and nearly a month since Caliburn.Micro has been upgraded. Well, I have finally caught up and upgraded the logging libraries. Caliburn.Micro.Logging, Caliburn.Micro.Logging.NLog, and Caliburn.Micro.Logging.log4net are now version 1.5 and available on NuGet. Version Changes Upgraded Caliburn.Micro to 1.4 Upgraded solution / project files to VS2012 Added support for Windows Phone 8 Split Caliburn.
Introduction I have been evangelizing the use of IoC for a number of years. Frequently the newly converted ask the following two questions: Which container to use? Which is fastest? My answer to the first is almost always the one you choose, and for the second question I refer them to Martin From’s IoCBattleweb page. I wont get into the reason for my answer to the first question in this post (I will save that for another day).