J2EE project execution best practices

ShriKant Vashishtha discusses three practices for resolving day-to-day software project execution problems.

In the article, J2EE project execution: Some best practices, ShriKant suggests that all J2EE projects should:

  1. Use template code:
    Among other benefits, he says that template code gives developers a ready reference and the template jump starts the coding effort.
  2. Perform automated code review:
    Instead of relying on manual code reviews, he suggests that teams make use of automated code review tools like JLint, CheckStyle and Lint4J.
  3. Write an effective developer’s handbook: ShriKant suggests that considering the long development times, attrition rates and varying developer skill sets, it is important to have a handbook to sort of get all developers on the same page. He also lists the things that should be part of a developer handbook.

Any thoughts on how effective these practices are, particularly on the rarely used practice of writing a developer handbook?

Related:
>> Four tools that make Java code review painless and effective
>> Books On Java Design Patterns and Best Practices

The following two tabs change content below.
Content Team

Content Team

The IndicThreads Content Team posts news about the latest and greatest in software development as well as content from IndicThreads' conferences and events. Track us social media @IndicThreads. Stay tuned!
Content Team

Content Team

The IndicThreads Content Team posts news about the latest and greatest in software development as well as content from IndicThreads' conferences and events. Track us social media @IndicThreads. Stay tuned!

  • raji.sapineni@gmail.com

    Any idea about multithreading using jbpm