Just finished with learning deep-Perl (classes, objects, tied variables ...). Seemed a reasonable step to support a mainframe-bound legacy environment. Have studied enough Java to just need to study specific elements.
Many possible next steps ... Ruby (on Rails), Python. Eventually many higher ... Groovy -- "and" but not officially "on" Grails-- ... Griffon.
Which seems a reasonable next step based on current job demands?
What are those current job demands? I'm a big fan of Perl. It certainly isn't "hip" anymore but I don't feel it is legacy.
Answers at least one question ... Perl is not "quite legacy". Means that knowing the deeper-details is not exactly a lost cause, just a bit of a short-bet.
I am planning on "beyond my UNIX/Perl/C" job frame needs. The newly developing job market is my concern.
Knowing only "legacy or near-legacy" technologies is not desirable.
steve359 wrote:
The newly developing job market is my concern.
Which market is that? Things are specialized and it is hard to get back the acronym hawks in front-line HR.
The iOS app market is still developing, but quite commodified. You can start your own business easily enough but getting hired may be more difficult.
Other than that, the rest of the market is web-based - all web-based. There are a few people still doing Perl, a few people doing C++, and people doing funky things like Rails and Python. The best way into those markets is to make a name for yourself working for free. Hopefully someone will like your work well enough to pay you to do more of it for them.
Professional groups also seem good places to get contacts, and to start being noticed.
Web-based is what I thought, unless you are "web aware" and work the back-end services, implementing DB services (for example). Or so it seems to me.
I like non-web concerns more than web-integration, but if that is the way the wind blows, then "propserous seas" are in that direction.
There is always "scrum master" ...
Thanks.
Opinions on next step in learning languages
