> 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).
*rofl* If you dont think that tools can improve productivity then I dont think you've been given the opportunity to use them properly. As one other poster does, I use IDEA, which has many features that increase the speed at which I can code. Emacs has many such features. The one tool that I argue is indispensable in J2EE development is XDoclet. Consider this situation. I have a SLSB that I want to change the interface for. Using a "standard" dev env, I would change the method, and then have to change the interface as well. ppl can forget to keep the two in sync - simple things that cause deployment/testing time problems. Using a tool like XDoclet removes this problem. Another common example. You change some code, and now an exception is being thrown and not caught. Tools like IDEA will pickup on this at development time, so that when you change the code, you are made aware of this situation and fix it before compiling. Tell me how often you compile, only to find some small problem, and have to recompile again after a quick fix for the problem. How long did that compile take? Wasted time. Whilst I agree with the rest of your post - I think the correct tools are absolutely essential in an effecient development team. cheers dim > 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".
