Jeff Makes Software

The software musings of Jeff Putz

  • Developers: You have to share and mentor others, for the sake of our profession

    Again this year, I did a couple of talks at Orlando Code Camp, the amazingly awesome free mini-conference that our local user group, ONETUG, has been putting on for a decade now. I am again fascinated by the vibrancy of our community, and all of the people who volunteer their time to share knowledge. It's humbling and amazing. (My decks are on GitHub, by the way. I won't rehash the mentoring and career development stuff here.)

  • EF7 RC, navigation properties and lazy loading

    Jumping into the brave new world of .NET as open source has been an experience, to say the least. The feedback loop is tight, things change quickly, and it's definitely a different world than the days of big bang releases. I think it's a great thing, but admittedly, it makes the early adoption thing a lot harder. Sometimes I find myself disappointed (as with the deferred release of SignalR 3, for example). Still, the scope of the frameworks and the number of people working on them is impressive, and I look forward to this new world.

  • Beating localization into submission on ASP.NET 5

    While I'm still enthusiastic about ASP.NET 5, there are things that I run into that seem way harder than they should be. Beta software, no docs, I know... I need to keep my expectations in check. Localization is just such a thing. The samples currently in GitHub along side the code lack context, especially relative to what we're all used to.

  • My last big Azure problem: The unexplained CPU spike

    Over the last year and change, I've written a number of posts about the challenges around moving my sites (primarily CoasterBuzz and PointBuzz) to Azure. These are moderately busy sites that can for the most part live in a small websites, er, app service, instance, with SQL Azure S0 for the data, some storage here and there, queues, and some experimental use of search, Redis and what not. I know I've done some complaining, but only because I really want one of the core premises of the cloud, namely for all of the maintenance and backend stuff to be abstracted away, to deliver without me thinking about it. Mostly, it has.

  • One year with sites in Azure

    My sites (CoasterBuzz and PointBuzz) have now been in Azure for about a year. It has been interesting, for sure. From a high altitude perspective, I can tell you that I've saved money when compared to renting a dedicated server, but there have been challenges in terms of reliability.

  • Repositories gone wild

    One of the very beneficial side effects of the rise of MVC in the ASP.NET world is that people started to think a lot more about separating concerns. By association, it brought along more awareness around unit testing, and that was good too. This was also the time that ORM's started to become a little more popular. The .Net world was getting more sophisticated at various levels of skill. That was a good thing.

  • The great Azure outage of 2014

    We had some downtime on Tuesday night for our sites, about two hours or so. On one hand, November is the slowest month for the sites anyway, but on the flip side, we pushed a new version of PointBuzz that I wanted to monitor, and I did post a few photos from IAAPA that were worthy of discussion. It doesn't matter either way, because the sites were down and there was nothing I can do about it because of a serious failure in protocol with Microsoft's Azure platform.