please dont rip this site

Rules of Programming in any Language

  1. Write self commenting code. Use variable names that are full words or common abbr. (note that "abbr" is not a common abbreviation)
  2. Write comments which remain true even if the code changes. E.g.
    GOOD: if (INPUT_PIN_1) { //Input 2 is data
    BAD: if (INPUT_PIN_1) { //Data pin
    (notice that pin 2 is the data pin, but the code was changed to test another pin instead. The bad comment will lead future programmer to think of pin 1 as data.)
    (notice that this is a bad example, because the constant should have been INPUT_DATA... see Rule 1 above.)
  3. Write lots of comments
  4. Retain lines of code which are bad for non-obvious reason as a warning to future programmers. Just comment them out and add the reason.

file: /Techref/language/rules.htm, 1KB, , updated: 2016/4/28 18:01, local time: 2024/7/17 12:10,

 ©2024 These pages are served without commercial sponsorship. (No popup ads, etc...).Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE. Questions?
Please DO link to this page! Digg it! / MAKE!

<A HREF=""> Rules of Programming</A>

After you find an appropriate page, you are invited to your to this massmind site! (posts will be visible only to you before review) Just type a nice message (short messages are blocked as spam) in the box and press the Post button. (HTML welcomed, but not the <A tag: Instead, use the link box to link to another page. A tutorial is available Members can login to post directly, become page editors, and be credited for their posts.

Link? Put it here: 
if you want a response, please enter your email address: 
Attn spammers: All posts are reviewed before being made visible to anyone other than the poster.
Did you find what you needed?


Welcome to!


Welcome to!