[xmlWiki-developers] coding issues

[Arnaldo C. <ar...@mi...>]

Folks,
    We're both eager and close to replacing a lot of this planning with =
coding.  I think the following issues will prove to be crucial to us:
    -->Refactoring<--  XP is known for letting the architecture =
"emerge".  This will only happen if we're diligent to "refactor =
mercilessly", one of the central XP practices.  Briefly, this is about =
having well-organized code, and constantly reorganizing it to the next =
level.  I think we all know what well-organized code is, but for =
interested parties, you can check out www.refactoring.com if you feel =
like it.
    -->Practices unique to our group<--  An environment where we're all =
in the same room is very beneficial for XP.  To make an XP project work =
with everyone spread out, we're all going to need to commit up-front to =
our own set of practices.  I think that these should be:
        a)After every coding session, email the group and summarize what =
you did.  This way we all have a gist of the code's current state.
        b)We've assigned groups different portions of the code, and this =
is probably a necessary evil, since we're all spread out.  But, keep in =
mind the XP practice of collective ownership.  Feel free to step outside =
the box of what you've been assigned and to work on something =
else...just let the group know what you did.
        c)Log into our xmlWiki chat space whenever you're coding.  This =
way you can ensure that no two pairs are changing the same portion of =
code simultaneously, and you can ask questions to other people currently =
coding.
    Let's try and agree to commit to these (or change them) up front.

Tonight's 8PM CST meeting:
    -Quick discussion of above practices/buy-in/change.  This should =
take 10 minutes, *tops*, hopefully more like 5.  If you disagree, have =
something to add or change or eliminate, speak quickly or forever hold =
your peace.
    -Initial design discussion.  According to "XP Installed", this =
should take no more than 10-15 minutes.  I say we should give it 30, =
tops.  Again, under XP, we should expect the first architecture design =
to be wrong anyway, and if we refactor mercilessly, it will be easy to =
change.
    -Someone will need to document our initial design in UML, and send =
it to the group.  Any takers?
    -Since we're moving into coding, I think our meeting lengths should =
be drastically reduced at this point (at least until the 2nd iteration). =
 If not, we're doing something wrong.

--Arnaldo
   =20