All Posts

Over the last month or so, I've been playing around with Swift, the new language that Apple unveiled at WWDC this year. Thus far, I've really enjoyed it. To get started with learning it, I thought I'd convert one of our iOS applications at work over to Swift from Objective-C. I'm only doing it in my spare time, so it might never get published, but I've learned a lot since starting.

So, I've been playing around with ASP.NET vNext... which sounds funny, because I haven't actually written any ASP.NET code yet. It's all been straight console applications so far. I guess it'd be more fair to say that I've been digging into the new KRuntime that ASP.NET vNext will be running on.

Last year at DevLink, I can clearly recall sitting in a session about Durandal and John Papa's Hot Towel VS template. My friend Michael Johnson was speaking. I was sitting two or three rows from the back because the room had filled up pretty quickly. We were about halfway into his presentation when I received the following text from my wife...

Microsoft has made strides in the realm of multithreading in the last few years by introducing things like the Task Parallel Library and now async/await support in C#. I thought it would be interesting to share some of my experiences in converting an existing WPF application over to use async/await.

About three years ago, our team migrated from using Subversion to Mercurial, primarily because of the pain involved with branches. If you've heard the phrase "tree conflict," then you know what we were dealing with.