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.
-
How to Work Remotely as a Software Developer
-
HTTP to HTTPS redirects on IIS 7.x and higher
-
Improving the security of your SSH private key files
-
Even though mouse-move, paint, and timer messages are generated on demand, it's still possible for one to end up in your queue
-
CPU core estimation with JavaScript
-
Announcing the release of AMQP support with Windows Azure Service Bus
Comments
Topnotch replied ago:
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.
Voters For This Link (11)
Voters Against This Link (3)