Java_Development
by
ironstorm
—
last modified
2006-01-19 03:31
Keep it simple, stupid. Do not try to desing too complex architectures if you needn't to Make your components really decoupled (considering Invertion-of-control technique) Write good javadocs!. They could be the only documentation of your code Instrument your code early. Application monitoring and management is a real need for every project. Consider using JMX since the very beginning of the project Test driven delopment. A class without test simply doesn't exist Analysis driven development. Always analyze your code during development. Check coding standards, bad practices, dependencies Continuously integrate your code. Every 6 hour automatically build and test your code Use a simple web-based bug/issue tracking tool Use jira or bugzilla to signal new issues
Forgot your password?
