On Sun, 12 Jan 2014 10:38:16 +0000, Orchid Win7 v1 wrote:

> This seems to be the main argument of the book. Anything non-obvious,
> either put it into a subroutine with a descriptive name, or make it into
> a variable who's name says what it's for. Basically, anything that isn't
> clear, slap a name on it to clear things up.

That doesn't address the situation that it may be obvious to you, but not 
to someone else who's reading the code.

In order to be effective at this, you have to put yourself in the shoes 
of someone who isn't familiar with what you're doing.  I've worked with a 
fair number of developers, and they don't always have that ability.

Jim

-- 
"I learned long ago, never to wrestle with a pig. You get dirty, and 
besides, the pig likes it." - George Bernard Shaw

Post a reply to this message