Cuddy never had House tutor her.

You don't hire an architect then butt in during planning to suggest using glass as your skycraper's foundation.

You don't scout for an F1 driver, then pull him aside to teach him the finer points of driving on the freeway during rush hour.

You don't ask a gourmet chef to cook you ham and eggs for your snack.

You hire experts then get out of their way because you need them to get their jobs done.

You don't hire a very good programmer then ask him to go back and comment his code (some of which, while pretty hairy, can be rather elegant) just so you can puff up your chest and prove to yourself that you've still got it (for any value of it).

You don't ask Einstein to go back to his equations that produced E=mc² and have him label each step with an essay. You accept that you're not in the same league as him when it comes to physics, and just accept it.

Sure, you can ask him to explain it, give a lecture on it. But no one can and/or should expect him to spoon-feed it to undergrads.

My objection is not to commenting code. I do that. I advocate that.

But, like any programmer worth his salt, I try to comment on the why, not the how. The documentation on the how part is IN THE CODE. If you're anywhere near a halfway-decent programmer, you would know this, without having to be told.

If You (yes, you; you know who you are) are going to be selling this code to somebody else, couldn't you at least find a buyer who's, you know, actually a programmer? Or at least has one on his staff? Preferably a programmer who's beyond the Hello, world! stage in the language we're using?

But, I suppose I shouldn't complain. After all, this is billable work, too.