So, I recently read Applied Software Project Management, by Andrew Stellman and Jennifer Greene. I absolutely loved it; here's the review I wrote for Amazon......

So, after my last post way-back-when, I got busy fixing bugs for a while. Then I decided I wanted to do something other than fix bugs, and switched over to the Hypervisor team. So for those who missed the announcement a few months ago: the hypervisor...

So I've checked in the new Longhorn threadpool. (Unmanaged). If you use the threadpool, I think you'll enjoy it; there are a number of API features which should make it very easy to write correct code which uses it, particularly in the area of cleanup...

(In this post, I demonstrate just how young I am; I'm sure this stuff's been hashed out many times over the years...) So, I like Hungarian notation. This puts me at odds with most of my colleagues, who intensely dislike it. The few times it's come up...

So I was visiting my parents the other day. They've been going through old boxes of stuff, simplifying a little, and had stumbled across the first home computer we bought: a Commodore 128. This was the state of the art when I was in sixth grade, I think...

... you'll probably forget to call _resetstkoflw() in your exception handler when it's a stack overflow exception. This re-establishes the guard page, so that the next time the thread hits a stack overflow, it'll get another stack overflow exception;...

I noticed another fun thing about structured exception handling the other day; it's probably old news to the compiler team, but I thought it was interesting. Imagine you have code like this: DoSomething(); // This may raise an exception. try { *x = NULL;...

A number of devs don't quite understand the order of operations in structured exception handling. This leads to some interesting bugs... Take this snippet of pseudocode, for example: try { EnterCriticalSection(); try { DoSomething() RaiseException();...