| galathaea 2006-10-16, 6:57 pm |
|
Ron Jeffries wrote:
> On Sun, 08 Oct 2006 14:20:00 -0700, galathaea@veawb.coop (galathaea) wrote:
>
>
> In XP, "communication" does not refer to establishing formal coding guidelines.
> While XP does advise communicating with the code (among many other ways), and
> does suggest that the team needs to code in a similar-enough way to make that
> communication possible, the real issues around communication in XP have to do
> with communication between one human and another, using conversation and many
> other forms, not just coding.
yes
but
xp _does_ promote the use of common coding style guidelines
i apologise if i attribute this wrongly to communications
which is one of the "values" of the process
in place of one of its "practices"
as this may be  attribution on my part
most of the books and articles on xp that i have read
though
do state this practice supports the communications value
and this is where my disagreement lies
although any given file
or usually any module or subsystem
should be consistent
an entire team shouldn't be asked to follow one style
this
i believe
can be a hinderance to agility in the long run
engineers are by nature very obsessive
and tend to become focussed on style issues over substance
this should be avoided
particularly at the level of codifying into process
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
galathaea: prankster, fablist, magician, liar
|