Does Python really follow its philosophy of "Readability counts"?

[Tim Rowe]

2009/1/24 Rhodri James <rhodri at wildebst.demon.co.uk>:


> My experience with medium-sized organisations (50-100 people) is that
> either you talk to Fred directly, or it doesn't happen.  In particular
> the more people (especially PHBs) that get involved, the slower the
> change will come and the less like your original requirement it will
> look.  Each person, no matter how technically adept, has a significant
> chance of misunderstanding what it is you need and/or expressing it
> poorly to the next person in line.

So you talk to Fred, and he changes the "pong" library function to go
"ping", as you wish. Unfortulately, neither of you know that Alice is
depending on Fred's "pong" library function to go "pong" as specified,
and is totally stuffed when he delivers it and it goes "ping". That's
why changes to specifications need to go through a proper
specification change procedure if the team (not the organisation) is
more than a few people.

-- 
Tim Rowe