The 10 commandments of coding conventions |
[Dec. 18th, 2008|02:32 am] |
- Thou shalt not place the Left Curly Brace on a line of its own; this shows disrespect to thy Fathers and thy Mothers who only had 80 columns and 24 lines in days of old.
- Thou shalt not use the GoTo, for such disrespects the Prophet of Programming Dijkstra.
- Thou shalt comment thy code, and provide great detail about the workings of thy mind when thou does first write thy method. And thou shalt revisit and revise thy comments only in the earliest hours of the morning prior to thy code review.
- Honor thy Sun and thy Java that your days may be long upon the Virtual Machine where thy code livith.
- Thou shalt Compile before checking in.
- Thou shalt Run thy code at least once before shipping.
- Thou shalt Test at least one Browser against thy Server's code, and thy backup Server's code, and thy Neighbor's Server's code.
- Thou shalt not covet thy neighbor's operating system unless thy neighbor runs Linux; If ye cast your eye upon thy neighbor's Windows Server, and covet it in thy heart, thy staff shall take thee into thy parking lot and stone thee with mice until the demon of stupidity leaveth thee.
- Thou shalt not make libraries of other gods such as C# or Perl. These are an abomination before thy God.
- Once thou hast compiled thy code, generated thy Java Doc, Reviewed thy code with the elders of thy people, Deployed thy code upon thy server, and tested thy code upon the Browser of thy God (Firefox 3.0), and thy customer doth stumble upon thy bug, thou shalt blame thy customer with thy mouth, and curse his existence, for thou hath commented, placed thy braces properly, indented with four spaces (and not eight as do the godless), hath capped thy constants, hath lowercased thy methods, and hath passed all thy JUnit tests… It is the truth of God that if yee hath done all these things, thy customer must be at fault.
|
|
|