I wish I could get to this point where I work, but his article presupposes a couple things: * You have tests. * People write code to be readable. Where I wor

I wish I could get to this point where I work, but his article presupposes a couple things: * You have tests. * People write code to be readable. Where I work, neither is the case. I try to write tests[1] for my stuff, and I try to write clearly. But I have to comment what I'm doing since the libraries and APIs I'm calling are so baroque and almost deliberately obfuscated, that I have to comment what's going on if for no other reason than self defense. [1] As a point of reference, in my current project we have something like 6 - 8 developers. Of the unit tests that exist, I've written 85% of them, and I'm embarrassed at how few I've written.