[Python-Dev] barry_as_FLUFL

[Nick Coghlan]

On Fri, Aug 6, 2010 at 2:25 AM, LD 'Gus' Landis <ldlandis at gmail.com> wrote:
> Hi,
>
>  I just read an interesting article (interview with Fred Brooks).
>  See: http://www.informit.com/articles/article.aspx?p=1600886
>
>  Eoin: The book contains a lot of explicit and implicit advice for those
>  who must manage design projects. What would your top three pieces
>  of advice for such managers be?
>
>  Fred:
>  1. Choose a chief designer separate from the manager and give him
>      authority over the design and your trust.
>  2. Plan for the iterative discovery and screening of requirements.
>  3. Prototype (or simulate with models, etc.) early and get real user
>      feedback on real use scenarios early and often.
>
>  I immediately thought of the Python "process" as a real life example
>  of this working!  Fortunately too, the "crop" of "manager"s is also
>  growing!

There's actually quite a lot open source and proprietary development
in general can learn from each other, but the fact that so many open
source developers *aren'* getting paid means that garbage that is
tolerated in a proprietary setting doesn't happen as much in open
source.

One random thing: the knowledge that your commits are going to be
broadcast immediately to anyone that is interested, as well as
archived permanently on the world wide web is a powerful incentive to:
a) write good code
b) comment anything that is hackish/tremendously complicated
c) write decent checkin messages

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia