Monday, May 10, 2010

Java Coding standard wars

Nick and I have had quite a few fights regarding some technical stuff. I guess I am educated too much by Yoav Shapiro, SDM06, as regarding spaghetti code theory. I have to say I am in totally agree with Yoav that that is total necessary in a start-up environment: get the stuff done first. Well, I sure have seen that in many startup companies;).

Nick, on the other hand, is from the dream world. Well, I have to say nick did teach me some good discipline over the years, such as demanding detailed comments when checking in code. No complain about that. However, I do think we can lose some trivial stuff, such as:
  • line length should be no more than 80 characters (he keeps formatting my code and makes me verifying every time ;)). Who cares in today's world: We all have big monitors and we never print code to paper (in order to save the environment;))
  • No underscore in class name. I am actually not sure if this is bad practice. Maybe it is.
  • Whether closing braces should be on the same line or not. Come on, I just like keeping it on the same line. It looks cleaner.
Anyhow, I suppose we should compromise and meet in the middle. However, I still think the first priority is to get the job done.

4 comments:

  1. Replies

    1. Hi, Great.. Tutorial is just awesome..It is really helpful for a newbie like me.. I am a regular follower of your blog. Really very informative post you shared here. Kindly keep blogging. If anyone wants to become a Java developer learn from Java Training in Chennai. or learn thru Java Online Training from India . Nowadays Java has tons of job opportunities on various vertical industry.

      Delete
  2. The objective of the Java programming dialect was to make it so that a designer who customized on one PC could run his/her code on another machine, regardless of the possibility that the two machines were nothing similar.
    web design lessons

    ReplyDelete