...but it's not the kind of math you might be thinking about, like calculus, etc. Rather statistics, discrete math, combinatorics, etc. are becoming essential skills if you want to be better than average.

It's hard to imagine how you determined that I was "incensed" when I was making an observation.

I'm glad you've been "instructed" so that you know what to call it.

Does anybody really care what he has to say about Mono & C#?

After fighting a decade+ long losing battle about Linux vs. GNU/Linux naming, he just enjoys trying to continue controlling others and telling them what to do and not do.

Contrary to some of the posts here, I think it's a good idea to pick one language to focus on, but to balance that with learning more general design/algorithm/etc. skills.

Don't get too caught up with the latest buzzwords. Do read a lot of books, and a lot of code, and do write small projects.

Pick one language, I'd suggest C++ or C#, to get very good at. As time passes buy every good book on that subject area, and really master the language and common idioms. Alternate time learning about that language with learning about more general things (operating systems, Win32 internals, Linux kernel, whatever you're interested in).

Consider the fact that you'll potentially be doing this for a very long time, and don't expect that you'll be an expert in anything in a year or two. It will take time. Hard work does pay off though.

My other suggestion is to read at least one soft-skill book for every two hard-skill books you learn, even if the soft-skill book is somewhat related to programming (e.g. a book on productivity for programmers). Examples would include books on time management, influencing others, communication skills, etc. Over time these skills pay off at least as much as the core programming skills, if not more.

As usual I fail to see how this is "stuff that matters." I guess it's time to turn in my /. decoder ring.