Dave Plummer

And so I finally put my phone number in the assert.

And I was like, if you see this message called APL at 425836, my phone number.

And finally, we did get a catch in the actual stress debugger that I was talking about earlier, where it happened to somebody with a debugger connected.

We were able to go through and it was actually a kernel accounting issue and it wasn't a task manager issue.

So they just fixed it in the kernel once I was able to prove that it was in fact the kernel issue.

And you'd think we would then remove my phone number, but we just commented it out.

So it's shipped and it's in all the damn source code leaks for NT that are out there.

So that's how I find task manager code is I search for my phone number on Google and it will...

Reverse find the empty source code.

A little facetious because it's probably not the smartest thing, but you will find out.

Yeah, I'm a little religious about my asserts, too.

I don't assert things that I hope aren't true.

I assert things that I know cannot be true.

And I think that's really the intent of an assertion, so I'm overstating the obvious.

But when it does occur, it's a bug, plain and simple.

It's not a warning.

Yeah, it's not something I want to suggest you go back and add later.

It's something you should do organically as you build your code.

So for each function, if you've got assumptions, like I know that this pointer is never null, well, assert that.

If you know this count is always less than twice the byte width, assert that.