Code style and code conventions

     Code conventions is a must-have part for all developers projects. If you want to keep a high standard of quality in the code you should write with common convention. I guess all real open source projects follow some convention, and it's right way.

     It’s not a secret that long term-value of software is in direct proportion to the quality of the codebase. During the lifetime of the program, it probably will be modified many times. If application has a clearly understandable structure, it's less likely that it will be broken with changes. Also it can help in reducing the brittleness of programs.

     Each project should have its own code/style conventions or follow the already written and all know rules.        

     And if you asking yourself about conventions, you must understand that it makes it easier to follow by the people who inherit it after you. Sometimes happens when code is really difficult to understand, then you should try and clean up the code to make it more readable.

     Often happens that the code does not follow good conventions, so it's hard to follow the precedent, but one of the main goals of a code style is consistency. Of course if you spend many hours to understand what a method does because it uses poorly named variables or something else, you should refactor as appropriate for the situation. But you should remember, if you introduce a different style into the code that is already consistent you lose that consistency.

    This is an example in general form, a set of coding conventions and rules for use in Java and GWT programming. So, this document describes how developers should write code. The reasoning of these styles and conventions is mainly for consistency, readability and maintainability reasons. All working file should represent the following conventions.

     Here is the link to my example of code convention.