Tools in the Java world have never been confused, but fancy tools may not be suitable for your team.
At the end of another project, we will summarize some of the most necessary tools to provide the greatest support.
See Chapter x of death travel 2nd-minimum toolset.
1. Support for refactoring, TDD, Debug J2EE applications, and the IDE prompted by Flying Error
A. refactoring: even if the team only uses Rename, Move, Extract Method, and other basic functions, there are too many things in the J2EE structure, refactoring will help you clean up things. After the dependency is formed, you are no longer used to relying on the compiler.
B. TDD: TDD is not equal to Unit Test. TDD eliminates the need for dependency on the presentation layer, manual data input, Data Clearing, and Tomcat development.
Our team cannot afford to test coverage for the moment. So and UntTest are just a development method, not a testing method.
C. Debug J2EE applications:
Web developers generally use System. debugging information is displayed in the out or log4j mode. However, for programmers who used to program on the desktop, they can directly enter the debugging mode and track the program execution path in a single step. If they want to see the variable, they can see the variable, it is a matter of good faith.
It's just that the IDE didn't support it.
D. Flying Error prompt:
Standard configuration of Java IDE. Prompt immediately when there are errors. Do not wait for compilation. Unfortunately, this is not a standard in IDE in other languages.
The team now uses IDEA 4.5.
Eclipse is enabled only when some plug-ins are used.
2. Comparison of version management tools and text difference/merge tools
In the past few years, do anyone dare to work with people without using version management tools? Yes.
A good Programer, in addition to good udpate/commit habits, will it make good use of text difference comparison/merge tools as another level of observation criteria.
In addition, version management tools must be able to work with IDEA (because it is useful for refactoring ).
We still use CVS, green-haired turtles, WinMerge. SubVersion, and so on.
3. Project plan, task allocation, demand change management, and Bug management tools
Project planning, task allocation, progress tracking, demand change management, and Bug management are almost all tasks of PM.
In the past, there were always a lot of software to manage these problems separately. Copy several Paste software for the same problem.
However, if your team's Project plan is in the XP plan style rather than the MS Project ---
Congratulations! a JIRA can complete all the tasks.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
