Link Details

Link 949551 thumbnail
User 225256 avatar

By mswatcher
Published: Apr 06 2013 / 02:44

The other day, I sat in on a meeting where a large-ish group was discussing “standards” for their particular area of software development. I have the word standards in quotes because, by design, there wasn’t a clear definition as to what sorts of standards they would be; it was an open-ended exercise. The standard could cover anything from variable casing to development practices and principles to holistic approaches.
  • 10
  • 0
  • 540
  • 465


Add your comment
User 282815 avatar

Infernoz replied ago:

0 votes Vote down Vote up Reply

The solution for code layout is to provide IDE template files for a project and have a style checking plugin in the Maven build; the only stuff people should normally need to read is about design and functional coding conventions, and other operational concerns. The only time people should need to refer to a code layout standard is when they need to configure an IDE template for a new IDE e.g. I detest the fugly mess which is Eclipse, IntelliJ Idea is not much better, so far prefer to use the cleaner interface of NetBeans.

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (9)

Voters Against This Link (0)

    Apache Hadoop
    Written by: Piotr Krewski
    Featured Refcardz: Top Refcardz:
    1. Play
    2. Akka
    3. Design Patterns
    4. OO JS
    5. Cont. Delivery
    1. Play
    2. Java Performance
    3. Akka
    4. REST
    5. Java