Goal for 2011: Do not learn another programming language
chopmode.wordpress.com
chopmode.wordpress.com
I totally agree that learning new programming languages is great, and can help someone get a lot of new concepts. It certainly is fantastic for learning to separate syntax from algorithms from styles of thought. However I have found that there is a point of diminishing returns.
There is only so much you can get from learning e.g. 5 different object models, at some point it is no longer new, just annoying and different.
This is doubly true and noticeable if your previous languages were all over the map -- say js, python, haskell, c, prolog and so on.
At some point, it becomes more useful to dive deep into other things. Are you a systems guy? Attack a kernel bug. Are you a network guy? Make a traffic classifier. (or want to learn them well...) Trying to learn a new language and a new problem is prohibitively expensive sometimes.
My general rule of thumb is: if there is nothing about the new language that excites me, find a different problem that does. If I have to learn that language I will, but I don't need to force it.
In this environment I was forced to use a new language every few weeks... Not usually glamorous languages (say Haskell) but more commercially common (and not so common) languages.
I found that my productivity was definitely hurt by the constant need to re-learn the details of how to accomplish simple tasks, like opening a file or figuring out where they hide the urlencode function.
That can get you into maintenance programming hell pretty quick. Your manager always thinks you're too slow (although other people doing the same job are even less productive) and you don't get respect, don't get a raise, and ultimately the walls squeeze in until you need to move on.
Personally I think the things you can ~do~ with software are more interesting. I think it makes more sense to pick a language that's "good enough" and focus on getting highly proficient.
BTW where would you say that Erlang belongs in this picture?
That being said, there are two reasons you would want to learn a programming language: to add it to your tool set or to learn the concepts behind it, either for personal gain or to apply those concepts in other languages. I really don't think I will ever use Common Lisp in a production environment, however learning the concepts in Common Lisp really influenced the way I code in, say for instance, JavaScript or C. There is no need for me to learn all the intricacies of Common Lisp in depth because I will never need that knowledge. However, you need to have a very good understanding of the tools you actually use every day.
In short, my advice is to keep learning new languages to discover new concepts but also keep learning more about the tools you use every day; they're equally important.
Other than that, I completely agree with your thoughts on this.
And despite that, it has plenty of interesting and fun parts like the implicit-interfaces type system, etc.
(1) Flask App (2) Django Apps (1) Ruby on rails app (1) Symfony / PHP app (1) Play framework java app (1) Perl Catalyst app
I wrote all these in the last two years or so, and just keep changing languages for no legitimate reason. I am sure things might improve if I focused on creating them all under one language, no matter what it may be.
I think part of the drive for many of us is, we don't want to be caught not knowing technology X. So we strive to learn, but that puts us into the jack of all category.
I'm making a conscious effort focus on other aspects of programming now - algorithms, data structures, ai, etc... I think that studying these in addition to learning Python && Javascript && Lua indepth will be a better learning experience.