Link Details

Link 881147 thumbnail
User 448255 avatar

By dotCore
via richardrodger.com
Published: Nov 21 2012 / 17:24

Every developer knows you should have a one, exact, coding standard in your company. Every developer also knows you have to fight to get your rules into the company standard. Every developer secretly despairs when starting a new job, afraid of the crazy coding standard some power-mad architect has dictated.
  • 11
  • 3
  • 473
  • 1569

Comments

Add your comment
User 265881 avatar

Topnotch replied ago:

0 votes Vote down Vote up Reply

Basically coding standards entire reason for existing is to protect incompetent developers from doing too much damage. Its better to have a skilled team of developers who you can trust to just go in and write reasonable code that works and that they don't need excessive babysitting for the projects they create. The worst part though is that the issues that coding standards are meant to solve aren't actually solved; bad developers still produce buggy code that some poor soul will need to rewrite from scratch. The key factor is the skill and capability of the developer and not the elaborate coding standard that really makes the difference.

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.

Java EE7
Written by: Andrew Lee Rubinger
Featured Refcardz: Top Refcardz:
  1. Design Patterns
  2. OO JS
  3. Cont. Delivery
  4. CI Patterns
  5. CI Tools
  1. Spring Integration
  2. Git
  3. Regex
  4. Java
  5. REST