Re: [Javacavemaps-developers] agile XP style development model

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

I wasn't saying I wont help. I was just saying I didn't want to participate in the 3d thing if that is the way you want to do it. It just doesn't interest me and I'm not getting paid. I will work on other aspects I find interesting, since that is why I am here.

IMO there are many libraries that are very common place in the industry and are worth throwing in to almost any app you work on big or small. These include Log4j, JUnit, some other Swing extensions. They make life easier and take less than an hour to learn. There are other libraries that take a little time to learn, but if your project is medium to large scale, they will save you a lot of time and headache in the end. A good example is where I work there was a web reporting server designed in tomcat for rendering reports from a program that collected data. This web report engine was pretty limited and had alot of javascript and stuff which was a bitch to maintain compared to java, it was all created from the ground up. Yet why reinvent the wheel? I eventually had to rewrite his reporting engine, we used JFreeReport this time. Development time was cut in half and the end result was much more detailed and robust. The original design was a waste of time.
 Morale of the story is, you shouldn't try to re-invent the wheel when you can go pick up a tire for cheaper than it takes to build a wooden wheel.

Also since this is an open source project, you will actually pull in more developers if you use the popular libraries in the field today, because they want to use them. They want to learn, they don't mind the complication. In fact most good programmers embrace the complication and think its fun.  

--- On Thu, 1/8/09, Larry Gray <jav...@ya...> wrote:
From: Larry Gray <jav...@ya...>
Subject: [Javacavemaps-developers] agile XP style development model
To: jav...@li...
Date: Thursday, January 8, 2009, 12:58 PM

Obviously each developer who joins an open source project, his mileage will vary with each type of problem and each type of solution, along with his Architect, Developer and Programmer skills sets. And his mileage will vary from api to api, from library to library.  Some developers for example may handle problems on a lager scale as quickly as new developers on much smaller problems.  Agile development limits the scale of the project as a whole and additions to the project as it moves along.  The problem is scale can not be arbitrarily increased in the name of  extendability.  The addtion of libs other than the standard api shipped with sdk adds bloat as well as complexity. For somoene who is used to that coding that lib instead of the standard lib, this seems only to this
 person as if the tradeoffs are imaterial.  About extendability. Refactoring is always necessary reguardless of the api's you begin with.  To think you can grab this wonderful extendable do it all lib and still not have to worry about refactoring is a little nieve IMHO.   Anyway under agile development model we can't up the scale based on a promise to help if that is done. However if I see I have help because task are being completed, thats a sign that the scale can be increased.  I will keep adding developers to this project until I find maybe a dirty dozen that seem to align themselve more with this process, the rest may simply watch and provide technical assitance sometimes if you really want to help. And maybe some will join in later as the project becomes more complex.

Thanks
 Larry Gray
la...@ar...





      ------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB_______________________________________________
Javacavemaps-developers mailing list
Jav...@li...
https://lists.sourceforge.net/lists/listinfo/javacavemaps-developers