Over the Christmas break I ported this blog app from the somewhat messy version it was in 2009. It was based on the first version of MVC, and I wanted to get to the new, but not final version. There is still work to be done...
- Comments are broken. Why? Because there is something broken in the hosting software for the runtime that works locally, but not on IIS and in Azure. They already committed a fix, but we won't see it until RC2, presumably next month. Basically, I need the user's IP address because I have to send it to Google for the CAPTCHA test, but that IP always comes up null.
- I still don't have a clever idea for the header. It's not impossible that the post-it notes may come back, but I have to think of something clever to make them scale down and be responsive.
- On the plus side, the response and rendering times for what was already a pretty simple app are considerably faster. The home page, with all of that text (last 20 posts) used to arrive in about 1.0s, now it's often under 500ms from Google's point of view. Individual posts and content pages were upwards of 200ms, now they get as low as 50ms. The database hasn't changed and is the "slowest" option, and there isn't any caching going on either. They've clearly optimized the shit out of the new framework.
- I did finally update the resume, and fix the content (my Vimeo imbeds were all broken with ancient markup).
- I need to get the canonical meta tags in there. I see Google starting to index it with the www. on the domain, which no one really does anymore.
Importantly though, I have a lot of notes for my next ONETUG talk coming up in about three weeks and I can start putting that presentation together. It's kind of a win-loss situation, in that I can only cover so much in an hour, and I can only cover so much in an hour. Since the topic is about finding the new stuff in these new projects and frameworks, I can prioritize and hit what I think the audience will want most.