Re: F# fsharp

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

> >> 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.
> >    
> We agree if we disregard the "time" variable.

Oh, good, we're not as far apart as I thought then.

> Any member can understand any code file *if they have enough time*.
> Sadly, it is not always the case.

I agree.  That's why I think pairing on that code is beneficial to the
whole team.  The intention is not to try and make everyone an expert,
but to impart enough familiarity with the code from the expert to the
novice that the novice isn't completely lost in the code.  Not every
defect or feature requires the expert, even if the expertise is
required to write that code (AI, physics module, etc.) in the first
place.  Take the example of a fence-post error (loop count off by
one).  Even experts can make this simple mistake.  If a novice has
enough familiarity with the code to find the offending loop, chances
are they can fix that bug without the expert's help.

> Other variables impact this, I suppose it is more true in c++ 
> metaprogramming (boost ?) than in, say, python.

That sounds like the same problem, just a differen area of expertise:
metaprogramming instead of physics or AI.

> > 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.
> >    
> Sometime it is not about the code but the underlying disciplines : 
> physics, AI , whatever.
> I don't like "star coders" and "divas" but it is not black and white.

I think the best team dynamics come where everyone has special
expertise that can lend itself to the project in some areas, but where
all of the team members have enough understanding of the code that no
one single person becomes a "blocking issue".

In modern software, team dynamic is becoming more important than star
divas.  The days of John Carmack coding the next hit in his garage are
long since gone.  Take a look at the credits of any game (even the
indie "non AAA" games) and you'll rarely see one person listed as the
programming credits.  This is true for almost all software in the
industry now and not just games.
-- 
"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