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."
In my last job I typically worked 12 hours a day and most weekends. Sometimes I would stay up until 2am to work on my DPhil. There is such a thing as not enough time to learn a new language.
I had a colleague who would use his work time to learn new languages irrespective of the technical justification. He would leave a trail of unfinished, unmaintainable, buggy code, but his resume looked great. There is definitely enough time if you are one of those people who is comfortable stealing it from their employer.
Two translators on a ship are talking.
"Can you swim?" asks one.
"No" says the other, "but I can shout for help in nine languages." Language Barrier
Two highway workers were busy working at a construction site when a big car with diplomatic license plates pulled up.
"Parlez-vous français?" the driver asks them. The two workers just stared.
"Sprechen Sie Deutsch?" The two continued to stare at him.
"Fala português?" Neither worker said anything.
"Parlate Italiano?" Still no response.
Finally, the man drives off in disgust.
One worker turned to the other and said, "Gee, maybe we should learn a foreign language..."
"What for? That guy knew four of them and what good did it do him?" Say It In French
Morris was going to Paris. It was the first time he’d ever been out of New York. He went to his friend Shlomo.
“Shlomo, what am I going to do? I don’t know a word of French.”
“Don’t worry about it.” Shlomo told him. “Just keep your sentences short and put *la* in front of the word. They’ll think you’re French and never know the difference.”
So Morris gets to Paris and orders “la Taxi” to take him to “la restaurant” and gets there without any problem. Thinking he has discovered the secret to international travel he orders “la borscht” shortly after which the waiter brings him a bowl of beet soup.
Morris is so impressed with this that he forgets himself and begins to speak to the waiter in English. “Isn’t it amazing,” he says. “I never studied French in my life and everyone in Paris understands me!”
To which the waiter replied, “Look schmuck, if I wasn’t la Jew from la Brooklyn, you would have just been served a bowl of “la dreck” instead of “la borscht.” Misspelled..
One spelling mistake can destroy your life!
A husband wrote a message to his wife on his official trip and forgot to
add ‘e’ at the end of a word…
“I am having such a wonderful time!
Wish you were her..!” This is a true story from the japanese embassy in US Mori-obama[^]
Good programmers have no problem learning a new programming language.
I would disagree. I consider myself far beyond just "good", and I have definite troubles wrapping my head around functional programming - monads, currying, etc. I get the concepts, but there still remains a disconnect for me to get to a deeper answer to the question, "why???"
Ok, that'll teach me not to be glib. I think I'm a good programmer, and of course, you're right that not everything comes easily to me. I guess my point is that learning a new programming language is primarily useful only if it achieves something concrete. I've recently enjoyed using linq (not a programming language I suppose) for a utility I was writing and it took me a while to wrap my head around it. In the end, I was thrilled that using it simplified my program significantly. So there was a reason to learn it, I spent the time to learn it because of that, like a good programmer should. To me, the choice to learn something new when it will provide concrete benefits is what makes a good programmer, rather than the converse, suggested by this question, that learning a new language for the sake of learning it makes you a good programmer. Anyway, I guess I'm rambling.
Anyway, great to hear from you. (You wrote nice things about the first article I contributed to CP 8 years ago ).
C/C++ (haven't done too much pure C)
VB.Net (in theory, I haven't tried to use it in years)
Probably more, those are just the ones off the top of my head. I don't have much trouble picking up a new language, I can usually get the basics down in a few hours. (Though I'm only fluent in C/C++, C#, Java, and Python, because I use those ones regularly.)
a bit of Java
sql (if xml and css count so does this)
I clicked "Simply no desire to learn another language", because unless I need to learn a new language for a job, or a new project, I don't have the desire, all of the above I learnt because there was a need.