Top tips every programmer should follow

10 Programming Languages You Should Learn Right Now

  1. PHP
  2. C#
  3. Ajax
  4. Javascript
  5. Pearl
  6. C
  7. Ruby and Ruby on Rails
  8. Java
  9. Python
  10. VB.NET

Top Ten of Programming Advice NOT to follow

  1. Use error codes instead of exception
  2. Use unsigned integers for values that can only be positive
  3. Design classes parallel to their physical counterparts
  4. Make sure your team shares a common coding standard
  5. Write lots of comments
  6. Use accessors or properties rather than public fields
  7. Use the singleton pattern for variables that you KNOW you should have only one instance of
  8. Be tolerant with input and strict with output
  9. Code all the corner cases immediately, cause otherwise you’ll never go back and fix things
  10. Design first, then code

If you are a project manager or team leader, you should answer those question.

The Joel Test: 12 Steps to Better Code

  1. Do you use source control?
  2. Can you make a build in one step?
  3. Do you make daily builds?
  4. Do you have a bug database?
  5. Do you fix bugs before writing new code?
  6. Do you have an up-to-date schedule?
  7. Do you have a spec?
  8. Do programmers have quiet working conditions?
  9. Do you use the best tools money can buy?
  10. Do you have testers?
  11. Do new candidates write code during their interview?
  12. Do you do hallway usability testing?

Six ways to write more comprehensible code

  1. Comment like a smart person
  2. Use #define a lot. No, a LOT
  3. Don’t use variable names that will mock you
  4. Do error checking. You make errors. Yes, you
  5. “Premature optimization is the root of all evil.” - Donald Knuth
  6. Don’t be too clever by half

2 Comments so far

  1. Kyaw Tun on May 23, 2008

    10 Programming Languages You Should Learn Right Now

    C#
    SQL
    Javascript
    Java
    Python
    Perl
    C++
    PHP
    Matlab
    Ruby and Ruby on Rails

    VB.NET

  2. Patrik on June 5, 2008

    “Use error codes instead of exception”

    I’m not too sure about this. There is a difference between *expected* and *unexpected* errors and should be treated as such.
    Use error codes and exceptions in the right place.

Leave a reply