Re: [Javacavemaps-developers] my style

[sean w. <wa...@ya...>]

I read a book on extreme programming. I personally think the pair programming is overkill. Having multiple people agree on an API then one person code then a different person write the test cases works well. As long as the higher level API is defined right and then tested for the agreed functionality you are set, but code reviews are good. That is about as good as I have ever gotten it, otherwise your just doing everything twice. 

I would agree with most of the planning of the XP methodology.

The design part of the XP method I would have some disagreements on though. I don't always think starting with the simplest solution is always the answer. I have had to write and rewrite many systems because the original solution was not extensible enough to support the incoming feature requests. Instead my opinion is to start with the simplest solution possible that doesn't sacrifice the possibility of extension in the future. For example their are certian groundlaying things I will do in most all of my applications. Alot of it just comes down to good OOP principals as well though. You should also be wary of rushing development without enough active planning.

~Sean



--- On Sun, 12/28/08, Larry Gray <jav...@ya...> wrote:
From: Larry Gray <jav...@ya...>
Subject: [Javacavemaps-developers] my style
To: jav...@li...
Date: Sunday, December 28, 2008, 7:31 PM

If anyone on the project can't stand the XP methodology, please feel free to remove yourself from the project if you think you can't contribute because of it.  I'd as soon see no one in the member list than to see members who simply don't want to help out because of the decisions I make.  I realize methodology can be something like Religion to some folks.  I'm not religious per say about this XP methodology.  But I see some good ideas there. Most developers I think want to start the project out by packing many features and advanced features and they want freedom to work ahead on uneeded features. etc. cowboy coding I guess you might say.  XP is a fairly limiting style.  You only do what is currently within you capability meaning (time/resources/quality/scope). A
 itteration is 2 to 3 weeks, its just for goal setting.  We would have several itterations inbetween minor versions. and several minor releases or more up to maybe 10 between major releases and version changes. You can always work ahead on your local computer and have something ready to contribute when the time comes.  I am going to try to keep the specs worked ahead as much as possible so we can all know whats coming up next.  

I guess idealy we should have one or two task for each person per itteration maybe.  Anyway if we are coding we are getting something done.  If we don't communicate we can't colaborate.  Let me know what your thoughts are other than.. "hi, I'm here to help, I see your an idiot so  I'm here to take over, o I can't so sorry. bye now"
 Larry Gray
la...@ar...





      ------------------------------------------------------------------------------
_______________________________________________
Javacavemaps-developers mailing list
Jav...@li...
https://lists.sourceforge.net/lists/listinfo/javacavemaps-developers