Re: F# fsharp

In article <[email protected]>,
    Lionel Barret De Nazaris <[email protected]>  writes:

> >> Working within a team implies that you shall use the tools that are used
> >> by the other team members. Doing anything else means you're creating a
> >> nexus of potential future problems.
> >>      
> > Pair programming is a simple remedy for the "singular knowledge" problem.
> >    
> Yes but it is costly and suppose an homogenous set of skills among the dev.

In my experience, two people working together are more than twice as
productive as two people working alone.

Furthermore, pair programming as a cure to the singular knowledge
problem doesn't presume that everyone need be an expert in order to
avoid singular knowledge.

> The most tricky part of a codebase is often mastered by a few, simply 
> because to get it you need some/a lot of experience under your belt.

I guess we'll simply have to agree to disagree, then.  I don't
subscribe to the idea that there are certain high priests of code that
are the only ones that can accurately apply hermeneutics in order to
understand their code.

I do subscribe to the idea that there are varying levels of creativity
and expertise among members of a team.  However, if a "star player"
can't explain his crafty code to anyone else, then you don't have a team.
Instead you have a high priest and a bunch of unquestioning acolytes.
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
 <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>

      Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
_______________________________________________
Sweng-Gamedev mailing list
[email protected]
http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com