4 ms·
I haven't found that, or anything even close to that, to be the case at all. Maybe it's a geographical thing? I'm on the East Coast and from what I can see, i
by mindcrime 12y ago
I haven't found that, or anything even close to that, to be the case at all. Maybe it's a geographical thing? I'm on the East Coast and from what I can see, if you have a "hot" skillset (Hadoop/Big-Data, MongoDB, Clojure, Node.js, Angular/Ember, etc.) you won't have any problem finding a job, regardless of your age.
Personally, I'm 41 with 15+ years of IT experience and I have never felt any sense of age discrimination at all. But, I'm also constantly working to keep my skills current, and I do a lot of things to make myself attractive and known in my area - speaking at events, writing articles, blogging, etc. shrug
My feeling is, if you're sitting at 15 years of experience and you've been, for example, writing Java code for 15 years, go pick up a Scala or Clojure book, or learn R or take the time to learn Hadoop, Spark, Storm, Kafka, MongoDB, etc. If you have skills that are "hip" at a moment in time, I don't think it's usually going to matter much how old you are.
OTOH, if you are a 15 year Java programmer who is still writing Java 1.2 code for a JSP based app that integrates with a COBOL book-keeping system on an IBM S/360, and you refuse to even look at that "new fangled" Java 1.3 or newer, then yeah, you might find yourself in a tough spot if/when they decide to turn off that mainframe.
- deleted 12y ago[deleted]
- ekm2 12y agoCan you recommend some good beginner books on Clojure?
- mindcrime 12y agoI haven't gone very far down the Clojure path myself, but Programmming Clojure[1] from Pragmatic Press is one of the ones I started with. The other one I used is Clojure in Action[2]. There might be better books out there (or not), those just happen to be two that I'm slightly familiar with. [1]: https://pragprog.com/book/shcloj2/programming-clojure https://pragprog.com/book/shcloj2/programming-clojure [2]: http://www.manning.com/rathore/ http://www.manning.com/rathore/
- escherize 12y agoI worked with the guy who wrote the Manning book my sibling commenter mentioned, and it's quite good. But if you want to jump into clojure quickly, I can't reccomend Clojure for the Brave and True enough. http://www.braveclojure.com/ http://www.braveclojure.com/
- sanre6 12y agoi like this book http://joyofclojure.com/ http://joyofclojure.com/
- facorreia 12y agoI agree, there's a difference between having 10 years of experience and having 1 year of experience repeated 10 times doing the same thing. Me, personally, I enjoy learning a lot and I get restless if I don't feel I'm developing my skills and keeping current.
- csmdev 12y agoYou do realize that you're basically dismissing experts because they specialize instead of learning the basics for another technology each year. Or has one year become enough to be an expert on something?
- facorreia 12y agoExperts learn.
- csmdev 12y agoLearn what? A new thing every year? How do they become experts then? Just because you learn a new language or technology doesn't mean you become better at problem solving. It just means that you can solve problems using a different tool.
- mindcrime 12y agoI didn't read that post that way... I don't think "the same year of experience repeated 10 times" actually leads to expertise. That phrase, at least the way I've always used it and the way I feel I've seen it used, is more like saying "somebody who just keeps doing the same thing over and over again and doesn't even attempt to learn anything new". Ie, it isn't just about not learning new skills, it also includes not improving existing skills and knowledge. At least, that's the way I always interpreted it.
- ayers 12y agoKeeping your skills current is probably the most important point here. Could you please explain when you do this. Are you in a job that allows this within production projects? Or is this all on your own time outside of your day job? I know some companies run internal projects with the specific aim to help upskill employees in new technology.
- mindcrime 12y agoAt this exact moment, I'm fortunate enough to have a dayjob where I get to do a lot of different things and learn new technologies, etc. But in the past, when I didn't have that option, I just worked on my own open source project(s) and did stuff at night and on weekends, to fill that void.
- csmdev 12y agoSo basically be a freelancer. Market yourself heavily and learn whatever language or technology your employer uses. At this point, why get a job? You can easily earn more as a freelancer or contractor.
- mindcrime 12y agoYeah, that's a very good point.
- geebee 12y agoThis is a good strategy. However, it does seem to raise a new question - why is this more common in IT than other fields (which may beg the question, is it in fact more common in IT than other fields)? Lawyers and Physicians, Dentists, Nurses, and Dental Hygienists, they all do have to stay current - in fact, I believe that they are legally required to stay current. Now, HN is a tech board, so we don't hear from nearly as many Dental Hygienists here, but I'm going to operate on the assumption that DH's, at age 41, don't encounter the same issues of obsolescence as software developers do. I think that a big part of this may be something Michael O Church described as "dimensionality" (in an essay on the relative scarcity of women in programming). http://michaelochurch.wordpress.com/2013/09/21/dimensionality-and-also-a-theory-about-the-rarity-of-female-programmers/ http://michaelochurch.wordpress.com/2013/09/21/dimensionalit... The dimensionality may be a factor here… just as the path to becoming a programmer is much more vague and subjective than in many other fields, so is the path to remaining relevant as a programmer. It's not that it's strictly harder, it's that it's much more ambiguous.
- dragonwriter 12y ago> Lawyers and Physicians, Dentists, Nurses, and Dental Hygienists, they all do have to stay current - in fact, I believe that they are legally required to stay current. Now, HN is a tech board, so we don't hear from nearly as many Dental Hygienists here, but I'm going to operate on the assumption that DH's, at age 41, don't encounter the same issues of obsolescence as software developers do. Because they are required as a condition of professional licensing to stay current (and have a documentary trail of staying current that matches and profession-wide accepted definition of what "staying current" means), which means that while there is some risk of being in a specialization for which demand is reduced, it is virtually impossible to not stay current in the manner expected in the industry without voluntarily choosing to abandon the profession. Consequently, its harder to have covert age discrimination with "not being current" as an excuse. > The dimensionality may be a factor here… just as the path to becoming a programmer is much more vague and subjective than in many other fields, so is the path to remaining relevant as a programmer. It's not that it's strictly harder, it's that it's much more ambiguous. Sure, but I don't think that is anything inherent in the subject matter ofprogramming that is less clear cut than, e.g., law, in those terms. Its just a difference in the social and regulatory context.