I agree with _most_ of what you state Andrzej. But tools ARE important too. If I give you VIM to work instead of EMACS, your productivity will fall. I'm now using IDEA4J, a very lightweight IDE that has impressive support for refactoring of classes, and I have doubled my productivity, especially since I'm most of the time in continuous improvement. I doubled my productivity thanks to the tool, and the fact I'm using the right architecture, have the experience, and made the right points to management and the client, in order to have them match their expectations with reality.
The problem isn't the tools; the problem is that managers need senior people at junior cost(or any other needs that aren't achievable in short-term) and they tend to _think_ there should be _something_ that handles it quickly just because _somebody has had the same problem before_, all of this being naive and dumb. Usually this kind of manager has no technical experience. But tools ARE important, and have its own place. Only lately we're seeing such tools becoming widely available at affordable prices(as opossed to TogetherJ 2 years ago, which was the only decent tool around having J2EE in mind). Anyway Ruberto, I'm still puzzled by your original post; the more I think about it, the more it sounds like you presented a _feature list_ instead of an architecture. Are you planning to develop such a product? ;-) If you're actually in need, then check out: http://store.yahoo.com/ http://www.activec.com/ They may be more worthwhile than J2EE per se in a tight spot. My 2c, JP > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]] On Behalf Of Andrzej Jan Taramina > Sent: Friday, September 06, 2002 3:13 PM > To: [EMAIL PROTECTED] > Subject: Re: J2EE architecture for ecommerce - URGENT > > > Marx said: > > > :) > > that is the reason i'm searching for such a tool. > > > > fine. lets get a feature list out for such a tool if it has > to exist. > > > > what do u think a development team needs while development, to make > > their life easy and much more productive with greater speed in > > development. > > I think this is the wrong question. My experience in > building hyper-productive teams has shown time and time again > that productivity is rarely related to tools > (beyond the basics). Tools (especially things like IDE's) > are an exercise in > wishful thinking that magic bullets exist to address the > productivity issue. They don't. (eg. almost half a million > lines of server-side J2EE code, in 9 months with 3.5 > man-years of developer time using only EMACS, CVS and a debugger). > > What generates high levels of productivity is clear > vision/leadership/architecture coupled with very experienced, > talented developers. The quandry is that there is no > shortcut to gaining "experience" nor any way to magically > transform jr/intermediate developers into seniors through the > use of "tools". > > The only way to solve your deliverables problem is to keep > hitting the pointy haired managers over the head till they > change the deadline or expectations to something more in line > with the experience levels and capabilities of your team in > the short term....and work on boosting the experience level > of your team in the longer run. Neither of these tasks are > easy, many times are not much fun and with the former, can > put your job at jeopardy, which might explain why so many > technicians fail when the graduate to management ranks. > > Sorry that I don't have a "magic" answer....but as I said, > the root of the problem is that the question is the wrong one. > > > Andrzej Jan Taramina > Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com ======================================================================== === To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
