All Posts

Ah, timeouts. At my previous job, I wrote quite a bit of code that dealt with threading. When dealing with threads, asynchronous operations, and performant UIs, you can't always rely on callbacks to get you the results of some asynchronous operation. Sometimes you also have to throw in some waits, particularly if the UI gets to a point before the callback has happened. Whenever I did have to write any code to wait for something (usually off an AutoResetEvent or a ManualResetEvent), I never wanted to actually specify a timeout. What would my application do if it timed out? Would I retry again? Would I just show the user an error? Instead of dealing with that question, I just made the wait last for the default... which in most cases is INFINITE.

The Mohundro family has some big news... our first child was just born a couple of weeks ago! Both mother and daughter are doing great!

I know what you're thinking... "did he just say 'binary data'? Like, 1's and 0's?" Well, yes, yes I did. If you're like me, the last time you actively had to do anything with straight binary data was in college when you were learning how to convert between binary to hex to decimal and back again. I would imagine that most of us run into hex somewhat frequently, but that we don't actually have to deal with binary data as often.

I don't usually do blog requests, but then again, I don't usually get blog requests. I've got a few friends that I email back and forth with regarding technology, programming languages or whatever else piques our interests. This particular time, my friend was complaining about the switch statement in C# versus VB.NET.

Surely you've heard of the Chrome OS by now? If not, well, Chrome OS is a new operating system from Google that "provides a fast, simple, and more secure computing experience for people who spend most of their time on the web."