10 consejos de programación que NO se deben seguir

Iconiza TeamUncategorizedLeave a Comment

Esta no es mi área, pero me pareció interesante compartir esta información.

1) "Design first, then code"

2) "Code all the corner cases immediately, cause otherwise you’ll never go back and fix things"

3) "Be

tolerant with input and strict with output"

4) "Use the singleton pattern for variables that you KNOW you should have only one instance of"

5) "Use accessors or

properties rather than public fields"

6) "Write lots of comments"

7) "Make sure your team shares a common coding standard"

8) "Design classes

parallel to their physical counterparts"

9) "Use unsigned integers for values that can only be positive"

10) "Use error codes instead of

exceptions"

Ver listado detallado en: http://www.chrylers.com/

Leave a Reply