![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(Re: the subject, I'm now flashing back to an old Dilbert cartoon. Dogbert asks what happened, Dilbert responds, nothing, he's just practicing in case something good ever *does* happen.)
In the past few weeks, I've
1) recognized that an XML "shredding" procedure was the root cause of performance problems, and that the problem wasn't with any other part of the server infrastructure,
2) realized that there may be unexpected behavior with (feature redacted) causing (behavior redacted).
3) Puzzled out a really tricky spinlock contention issue, and
4) maybe figured out the root cause of a long running case that might come down to a faulty driver.
Every now and again, it does me good to remember that I'm *really* good at my job.
In the past few weeks, I've
1) recognized that an XML "shredding" procedure was the root cause of performance problems, and that the problem wasn't with any other part of the server infrastructure,
2) realized that there may be unexpected behavior with (feature redacted) causing (behavior redacted).
3) Puzzled out a really tricky spinlock contention issue, and
4) maybe figured out the root cause of a long running case that might come down to a faulty driver.
Every now and again, it does me good to remember that I'm *really* good at my job.
