2 ms·
While I think that most of the points the author makes are valid, I'd disagree with this: "On top of all this, the language that you thought was the next big t
by greenyoda 12y ago
While I think that most of the points the author makes are valid, I'd disagree with this:
"On top of all this, the language that you thought was the next big thing was a passing fad and nobody is using it 5 years later. Now you’re on to the next cool language, which might not be used 5 years from now. You constantly have to stay on top of things."
In most areas of programming, there's no need to chase the next hot language. Many of the languages being used today, such as Python, Ruby, Java, JavaScript, C++ and C have been around for a very long time. Outside of web and mobile development, the frameworks and libraries don't change that quickly.
"There’s a ton of stuff you need to know, and it keeps changing! It’s not something you can be truly great at unless it’s your main focus. You can’t be a 'weekend programmer.'"
There are many fields in which you can. For example, if your weekend project is writing a program to do electronic music composition on a PC or a Mac, you'll be pretty much unaffected by the trends in languages and frameworks. The code you write this year will still run just fine five years from now, and user interfaces on desktop machines won't change all that much in the next five years.