Anyone who can program say, C#, VB and SQL should know enough to pick up almost any other language out there in a couple of hours.
Anyone who has written C# should be able to pick up JAVA almost immediately, and vice-versa - in fact most C based languages should fall in very quickly.
Anyone who knows VB, also automatically knows most flavours of BASIC, and the VB derivations (VB6.0, VBA, VB Script, VB.NET etc)
I prefer not to define programming knowledge by the number of programming languages known, but rather the various types and specialties of languages, such as RAD, managed, object-oriented, scripting, query (eg PL/SQL, SQL), markup, procedural, mathematical/functional (eg F#), graphical (eg HLSL, OpenGL, LOGO) etc.
Obviously to consider yourself a master at a particular language you need experience with it's specific peculiarities (eg, users of C# will probably trip up on pointers, macros and headers if they move to C++) but the broader part of any programming knowledge and experience transcends language and syntax.
Also, I agree that while you might put XML and HTML down on your CV, they are markup languages, not programming languages (any logic implemented by a HTML page is written in VBS or Java Script)
You could probably draw a long bow and consider XSL a type of programming language as it has conditional statements, iterators and flow control, but you couldn't build a mail client with it or use it to organize your cd collection.
In some point in life you'll see that there're more important things to do!
There's life before and after work specially if you have friends, wife, kids, ...
I used to spend a lot more time in front of a screen than I spend today.
It's just not good for our health in general.
Not that long ago human beings were chasing animals with bows and arrows, riding horses and partying around without fancy cars or houses to pay for.
Evolution takes millions of years, not thousands.
Our body isn't shaped to be seated 18 or 20 hours a day.
We need to exercise.
Our eyes aren't prepared to spend that same amount of hours staring at something 50 cm (or less) in front to us.
I don't even want to talk about sleeping amount of hours and specially the period of the day you sleep
It's very different to your brain to sleep during the night than being in front of a computer all night and then go to sleep a couple of hours...
This list goes on and on...
Don't get me wrong, I've done this, a lot, and I still do sometimes, but now I really care about these things.
So whenever I have to spend extra time in front of a computer it really must worth it.
My body and the ones that I care about thank me a lot!
When you started (like I did) with a C64 you usually know BASIC and 6510 Assembler. At school we had Turbo Pascal. During my apprenticeship as skilled worker in electronics we used 8085 Assembler and TP again. Doing Perl then was my own Idea. When studying CS I used C++, Java, C, SQL. I should have learned haskell, matlab and x86 Ass as well, but I don't remember much about that. First contact with .net happened when working for two years for the chair of automatition (porting from VBS to VB.net).
Learning new languages is exciting (I'm throgh the ruby chapter of 7 languages in 7 weeks) and you learn about new concepts. They open your mind, even if you don't get fluent in those languages.
There are limits to the utility of doing anything better if you are already great. To ask why somebody doesn't do more of something presumes that it would be significantly beneficial, which it may not be.
Rather than spend my time learning yet another programming language, I am currently spending my free time: exercising, watching Lost, working on a personal project, and learning French. Spending several years of my life learning as much about programming as I could was very fruitful, but now I know enough that I want to spend most of my free time doing other things.
Sometimes you need to stop running, and just enjoy the scenery.
1 day, and I will be able to write programs with Visual Basic.
1 year, and maybe I know the most important libraries.
Knowing the language is as far as not enough to write *good* programs.
I am programming with C# about 3 years know, and there are always new classes I didn't even see before (e.g. simple, but rare ones like "StringReader" or more exotic ones like "ResolveNonMSBuildProjectOutput").
If you find spelling- or grammer-mistakes, please let me know, so that I can correct them (at least for me) - english is not my first language...
exactly it is. how long does it take to learn the basic of a programming language?
if a dumb f*** like me can learn php basics in one sitting (of course before that i finished my course in c,c++ and assembly in university). after learning c and c++ all programming language grammar seems similar. but to do real thing its matter of experience.
I know more that 3 languages, all mostly learnt while at work. I feel that my "first language" which I'm employed for is the one that will take me the furthest in my career. Thus, learning it and becoming a specialist in it will pay off the most in the company I'm working in.
"Program testing can be used to show the presence of bugs, but never to show their absence."