In light of the last two articles, it might be interesting to note that I spent four hours yesterday helping with “due diligence” (a.k.a. “butthole inspection”) evaluating some technology from another company. This sort of thing has become a semi-regular part of my job, but this is the first time I’ve been asked to do an actual code inspection in that context. I was very impressed with the code I saw, which met pretty much every criterion I’ve just described for good code. I’d even say it was better code than most of what I write, though the spec was a little scant. If you’re reading this, M, kudos to you!