Top tips every programmer should follow
10 Programming Languages You Should Learn Right Now
- PHP
- C#
- Ajax
- Javascript
- Pearl
- C
- Ruby and Ruby on Rails
- Java
- Python
- VB.NET
Top Ten of Programming Advice NOT to follow
- Use error codes instead of exception
- Use unsigned integers for values that can only be positive
- Design classes parallel to their physical counterparts
- Make sure your team shares a common coding standard
- Write lots of comments
- Use accessors or properties rather than public fields
- Use the singleton pattern for variables that you KNOW you should have only one instance of
- Be tolerant with input and strict with output
- Code all the corner cases immediately, cause otherwise you’ll never go back and fix things
- 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
- Do you use source control?
- Can you make a build in one step?
- Do you make daily builds?
- Do you have a bug database?
- Do you fix bugs before writing new code?
- Do you have an up-to-date schedule?
- Do you have a spec?
- Do programmers have quiet working conditions?
- Do you use the best tools money can buy?
- Do you have testers?
- Do new candidates write code during their interview?
- Do you do hallway usability testing?
Six ways to write more comprehensible code
- Comment like a smart person
- Use #define a lot. No, a LOT
- Don’t use variable names that will mock you
- Do error checking. You make errors. Yes, you
- “Premature optimization is the root of all evil.” - Donald Knuth
- Don’t be too clever by half
10 Programming Languages You Should Learn Right Now
C#
SQL
Javascript
Java
Python
Perl
C++
PHP
Matlab
Ruby and Ruby on Rails
VB.NET
“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.