I want to disagree with few things though…
1) “Never ever have more than one blank line”. I found out that both single and double blank lines do help to read the code, if you stay consistent. While single blank lines are good for dividing logical blocks of code, doubled blank lines might be good for separating methods / functions.
2) “Possibly, use 8-chars wide TABs to indent. If you find yourself going beyond 80 rows too often, then that could be an indication that there might be some design flaws in your program”. 2– or 4-chars seem to be more common (I stick to 4). Also “80 columns” for a row might be not enough in some cases / languages (you gave an example of classname, “ClientMessageOperationsBasicFunctor”, which alone is 35 chars — add some indentation, neat name for a defined variable, creation of object, … and you are way over 80 chars). I agree that one should not write lots of long lines, but “80 columns” should not be considered a long line anymore. Have also seen a code where someone divided long lines into more lines just to keep them shorter — it may be very hard to read. Greatly depends on situation, though.

I’m a newbie here.

So i’d like to ask you if your income reduced because of the world financial crisis?