News for hackers. Stuff that matters.
Re:The Mid-Career Crisis of the Perl Programmer by mratzloff on Monday March 10, 2014 @11:22AM (#7373410)
A note on labeling yourself a "Perl programmer", or an "<insert specific language here> programmer":

A marketable skill is an investment. If you specialize in one skill it may be very profitable--for a time. Like investing in one stock while it continues to increase.

Diversification is the only smart strategy if you're in it for the long haul. Keeping a portfolio of tried-and-true but also fashionable up-and-comers is the approach I've used to great effect.

As a bonus, it can also improve your skills in your existing languages.

Re:The Mid-Career Crisis of the Perl Programmer by sspiff on Monday March 10, 2014 @11:55AM (#7373635)
I was struck by the same impression: why label or restrict yourself to a single language? And why label all other languages as short-lived, low quality fads? Because that's what reading the two "tl;dr" sections at the top indicate. He's not doing himself any favours with that kind of statement.

When people (recruiters or otherwise) ask me what I do, I'm a developer. Not a C programmer, not a Rubyist, or any subset of software development. I know how to program, I know how to solve problems, and I know how to learn new languages, libraries or frameworks. Sticking to your guns in an industry as ever-changing, for better or worse, as ours, is a bad idea.

When I was a student, I was interested in trying out tons of new languages. I eventually ended up sticking to Ruby for most of my own projects. At university, we used Java almost exclusively. My two last jobs however, have been C and C++. I'm fond of C, but not a big fan of C++. If I had stuck to Ruby or Java, I doubt I'd have a job as interesting as the one I have now, as those to languages seem to be restricted to web development and things like low quality internal applications used by banks in my area.

(Unrelated: odd, I'd never hear of this guy chromatic before today. I was listening to music by Chromatics, and five minutes before this thing hit front page, I decided to Google the bands name, and I ended up on his Wikipedia page.)

Re:The Mid-Career Crisis of the Perl Programmer by jimejim on Monday March 10, 2014 @01:43PM (#7374426)
Well, there's a popular term now for some HR people called T-shaped people. The idea is that you are a generalist that has some deep knowledge in at least one specific area. It's not a bad idea to pick one specialization if you are interested in something.

The person in this article needs to adjust the language to emphasize that he knows about the rest of the world outside of Perl, but just happens to have a strong background there.

Re:The Mid-Career Crisis of the Perl Programmer by pekk on Monday March 10, 2014 @12:03PM (#7373682)
Why refuse any specialization? Some things take years of experience in a language to get right.

First, nobody should care that you can "hello world" in more languages.

Second, you don't have any preferences about what tools you use?

Re:The Mid-Career Crisis of the Perl Programmer by sspiff on Monday March 10, 2014 @12:28PM (#7373875)
Of course I have a preference, but in general you work in teams, and the quality of the code base and standard practices of the group are more defining in how fun or productive something is to work on than the choice of language.

I know nobody cares if you can write "hello, world" in many languages, but I never stated that or anything like that, did I?

Some things take time to learn (systems programming, memory management, ... are things you'll have to wrap your head around when coming from a higher level environment, for instance), but hardly any of them are language specific as far as I can tell. Feel free to point out examples to the contrary, although I feel like if it's hard to learn a general concept in a specific language, that sounds like a language design problem.

In many cases being a good programmer in one language means you can learn another language and become a proficient or good programmer in it relatively easily. Some specialization is fine, however, if you really stick to a single language/framework/environment, I think you're staking an awful lot on something that could mostly go away in five years time.

For example, I work in the embedded domain. Ten, fifteen years back, microcontrollers were pretty much king. You wrote software close to the metal, without an operating system, and allocated all memory statically. If you stuck to that kind of development, and refused to learn embedded Linux stuff or dynamic memory management, you'd be unable to find a job today (at least in my area, I can't speak for the entire world in this case.)

Re:The Mid-Career Crisis of the Perl Programmer by avar on Monday March 10, 2014 @01:50PM (#7374478)
You're right about a lot of this knowledge being transferable, but I think you might also be underestimating just how much useful specialist knowledge you can acquire specific to a particular toolchain, and how much of a step back starting over can be.

I happen to have been doing Perl professionally for a while now and I'd say it would take me at least 2 years to get equally up to speed on another toolchain.

Sure I can write programs productively in other languages, but with my language of choice I don't have to look up dozens of little things a day, avoid common and less common pitfalls all the time, and generally choose the easier path the first time around because I've been around the block a bunch of times.

No matter what toolchain you use productivity at that level is hard to come by, and a lot of it is toolchain-specific. I can competently hack C but someone who's been doing it for 10 years will run laps around me.

So while I'm certainly not married for life to the toolchain I'm using I also think that many people underestimate just how much effort it is to truly become completely intimately familiar with some tool, and how much you constantly gain in productivity for having done so.

Re:The Mid-Career Crisis of the Perl Programmer by Arnor on Monday March 10, 2014 @06:35PM (#7376130)
That's exactly why it's useful to get familiar with multiple toolchains. If you are pretty comfortable with Ruby and move to Python, you'll have a pretty good idea about what pitfalls you'll encounter in a dynamically typed, interpreted language. Of course there's a learning curve, but it's less intense for languages with similar building blocks.

The first homework assignment when moving to a new language/stack is to google: "<language/stack/whatever> fucking sucks" and read the first 10 pages or so, you'll get a sense of the pitfalls.

Re:The Mid-Career Crisis of the Perl Programmer by avar on Monday March 10, 2014 @07:34PM (#7376420)
I can easily switch between dynamic languages, including Perl, Python and Ruby.

What I'm talking about is the level of toolchain familiarity where e.g. you can look at a given piece of code and know exactly which opcodes it'll get compiled to, what algorithms those opcodes will employ, and by extension how everything else in the system works.

Now I certainly don't pretend to know all of that with Perl, but once you have that level of intimate knowledge that extends way beyond just the differences between similar languages with similar building blocks you'll reach a level of mastery that you don't want to give up easily.

If you accept a job at a new company you might have to start to understand tens of thousands of new lines of code to have a proper understanding of the system you're working with.

Similarly the hairy bits of programming language toolchains are tens to hundreds of of thousands of lines of code that you have to understand to truly know how they work.

My point is that assuming that you can easily transfer that knowledge on a whim just because you can read the syntax introduction of some new programming language is folly.

The toolchain is more complex than most people give it credit for, and mastering it matters.

Re:The Mid-Career Crisis of the Perl Programmer by rwallace on Tuesday March 11, 2014 @09:14AM (#7378988)
Sure. I don't think anyone is saying there's no value in mastering the toolchain.

But the OP was talking about blowing his life savings on a bakery because he couldn't find a job programming in Perl. If you ever find yourself starting to think like that, a big red flashing sign with the words 'Warning: excessive attachment to a particular tool!' should be lighting up in your mind.

Re:The Mid-Career Crisis of the Perl Programmer by chromatic on Tuesday March 11, 2014 @01:59PM (#7380968)
But the OP was talking about blowing his life savings on a bakery because he couldn't find a job programming in Perl.

No, he wasn't. The article isn't about Perl. The article is about the excessive attachment to novelty and reinvention as practiced in much of the programming world today.

Re:The Mid-Career Crisis of the Perl Programmer by mikegrb on Tuesday March 11, 2014 @06:42AM (#7378428)
> What I'm talking about is the level of toolchain familiarity where e.g. you can look at a given piece of code and know exactly which opcodes it'll get compiled to, what algorithms those opcodes will employ, and by extension how everything else in the system works.

Indeed, and I can say for sure the author of the post has such a low level knowledge of Perl.

Re:The Mid-Career Crisis of the Perl Programmer by Arnor on Tuesday March 11, 2014 @12:34PM (#7380361)
I agree completely. This is particularly prescient for me because I finally made the leap from PHP to Ruby with a job I started 2/5/2014 (hold your applause :P). There's a lot to learn, but I actually find myself more happy and productive. Also, I'm a bit of a junky for learning new tools and the like so that's part of the fun.
Re:The Mid-Career Crisis of the Perl Programmer by kbenson on Tuesday March 11, 2014 @12:41PM (#7380420)
I think the trend is that generally people are happy with the new language when they learn it because they want to. It gives you a chance to assess the warts of the previous language by seeing a new way to do things (and eventually an appreciation of what they did right but is problematic in the new language).

When moving to a language you aren't really enthused about, it can feel like all downsides. For me that was having to dive deep into some PHP projects. Although that may have been more to do with the nature of going from Perl to PHP, which really, really felt like regressing to me (PHP sort of feels like a very old, constrained version of Perl). I think the only feature I preferred in PHP was classes, and that point is more than moot now, it's reversed.

Re:The Mid-Career Crisis of the Perl Programmer by existencebox on Monday March 10, 2014 @12:23PM (#7373826)
I think the statement was more like, "a developer uses the right tool for the job, a perl programmer will always use perl". (to the above poster, I hope I didn't misinterpret...)

You need both, I think. Breath and depth. Excessive depth to the point of self identification as an "x" coder has often correlated with living in an "x" bubble in people I've met.

I have some thoughts on this (which I'm badly composing now due to being in a rush), it's a really important conversation to have (what's the right balance between breath and depth) and frankly depends a LOT on the person/work. I would certainly fucking hope that, to give a strained example, my brain surgeon wasn't just a general practitioner with a hobby :P

Re:The Mid-Career Crisis of the Perl Programmer by jakejake on Monday March 10, 2014 @10:02PM (#7376984)
I get a sense that some people change languages or frameworks frequently just due to boredom, inability to commit to any one thing or a desire to pad their resume with buzzwords.

It's just like everything else - great programmers will tell you to learn multiple languages to expand your mind. Mediocre programmers will twist that around and use it as rational to flip-flop around without developing any deep knowledge.

Re:The Mid-Career Crisis of the Perl Programmer by weavie on Monday March 10, 2014 @12:19PM (#7373793)
I think you should specialize in programming concepts first and specific languages second. Once you have a deep understanding of lambda calculus, mutable/immutable state, lazy/eager, classes/functions and all that, then first it is easier to approach any language and second you will have a much deeper knowledge of the languages (yes it should really be more than one) you do specialize in.
Re:The Mid-Career Crisis of the Perl Programmer by goostavos on Monday March 10, 2014 @12:42PM (#7373974)
>As a bonus, it can also improve your skills in your existing languages.

I'd actually say that doing so is the easiest way to grow stylistically as a programmer. Each language has their own way of doing things. Some of those things are done really well, others, well, not so much. If you've never dipped your toe outside of the core language pool, it's tough to know just what those things are.

Every language I've ever learned has opened my eyes to a new way of doing things. As a guy who cut his teeth on Python, I'd say that I didn't really "understand" hardcore OOP until I picked up Java. You just don't see that every-noun-is-now-a-class style often in Python. Closures "clicked" when I picked up Javascript, and really deep lambda use didn't really sink in until I picked up Scala.

I had, of course, always used these things in Python, but only on a surface level. Exploring an environment where some small feature of your primary language is the big common feature of another is very eye opening. You pop out the other side with tons of new knowledge and usage patterns.

Re:The Mid-Career Crisis of the Perl Programmer by viraptor on Monday March 10, 2014 @12:51PM (#7374034)
> As a guy who cut his teeth on Python, I'd say that I didn't really "understand" hardcore OOP until I picked up Java. You just don't see that every-noun-is-now-a-class style often in Python.

This sounds really weird to me considering that almost every noun is a class in Python, but that's not the case in Java (primitives are not classes and there's no easy to use meta-class construction).

Re:The Mid-Career Crisis of the Perl Programmer by goostavos on Monday March 10, 2014 @01:01PM (#7374113)
You're right, everything is an object in Python. However, what I'm referring to is more on the application design side that you see in the enterprise Java community, rather than the implementation of the core types or builtins.
Re:The Mid-Career Crisis of the Perl Programmer by midas007 on Tuesday March 11, 2014 @07:04AM (#7378497)
Hopefully this offends everyone &| starts yet another pointless religious debate: Java was a reaction to C/C++ (language safety); Python was a reaction to Perl's messes; and Ruby is polished Perl. And bonus: Go was a reaction to Java and C++ compiles taking forever.

With production usage, each platform matures through attempts to learn from the past while not forgetting too much before that.

(Sadly, though most everything will be coded in javascript.)

Re:The Mid-Career Crisis of the Perl Programmer by kbenson on Tuesday March 11, 2014 @12:11PM (#7380168)
There's hope! With a sufficiently complex caching and verification system, we can deploy chunks of JS that implement interpreters in-browser, last a long time, and can possibly be pre-compiled into an optimized form.

If we really view JS as assembly for the web, I think there's an interesting future.

Re:The Mid-Career Crisis of the Perl Programmer by codygman on Monday March 10, 2014 @07:55PM (#7376517)
I would call Java hardcore class-based/design pattern programming more than hardcore OOP. If you want hardcore OOP try smalltalk or Common Lisp's CLOS.

However I agree that going from Python to Java can seem like hardcore OOP. It's tempting to argue that hardcore OOP is relative, but I like to go by Alan Kay's definition which is pretty easy to prove/disprove.

Re:The Mid-Career Crisis of the Perl Programmer by badman_ting on Monday March 10, 2014 @12:26PM (#7373865)
He does seem unusually determined to remain a Perl programmer. I liked how he threw in the JS renaissance as somehow relevant to Perl because they're both from the 90s or whatever, a bit delusional if you ask me. It's painful to move on from the platform you spent so long mastering, but sometimes you gotta do it.
Re:The Mid-Career Crisis of the Perl Programmer by singingfish on Monday March 10, 2014 @04:36PM (#7375531)
No i disagree with your interpretation, but that's because I'm a perl guy who is currently doing 60-75% javascript. Both are very pragmatic languages with significant design warts, but with enough useful higher level features to make them fun (unlike say PHP).
Re:The Mid-Career Crisis of the Perl Programmer by inquist on Monday March 10, 2014 @06:37PM (#7376134)
singingfish, I'm curious what you have in mind here. I've used each of these a bit and I haven't noticed PHP lacking high level features?
Re:The Mid-Career Crisis of the Perl Programmer by singingfish on Monday March 10, 2014 @07:34PM (#7376421)
It's not introspective enough compared to the other big dynamic languages, it suffers from a lot of low range developers working on it, the namespacing is a mess (which leads to to the docs although relatively thorough, but a mess). My understanding is that things like CakePHP are an improvement, but given PHP's underlying design a bit of a shim. Don't get me wrong people do interesting stuff with php (especially the pornographers), but it's a kludge. I also don't like the tendency for close binding of code with a real web server that I've observed.

Bear in mind my most recent PHP experience has been bending wordpress to do my will (taking over a project that's had the designer on the lead), and dealing with an undocumented not-quite-webdav implementation written in PhP that seemed to be overly dependent on apache.

Re:The Mid-Career Crisis of the Perl Programmer by girvo on Monday March 10, 2014 @11:03PM (#7377175)
CakePHP is not an improvement, and the fact you'd bring it up sort of shows you don't use the language much if at all...
Re:The Mid-Career Crisis of the Perl Programmer by singingfish on Monday March 10, 2014 @11:06PM (#7377180)
Yeah should have said 'cake php or whatever' I don't know what the latest and greatest is, but I know cake was one of them not that long ago. But the PHP I've had to maintain recently has had most of the old problems of perl style CGI with the disadvantage of a lack of the extremely good toolchain that perl has.

And PHP's design flaws are at the core of the language without the extendability that perl has.

Re:The Mid-Career Crisis of the Perl Programmer by hibbelig on Monday March 10, 2014 @06:23PM (#7376088)
He is part of the Perl community, that's why. He not only uses Perl, he shapes Perl. Would you (easily) move away from something you helped shaping?
Re:The Mid-Career Crisis of the Perl Programmer by collyw on Monday March 10, 2014 @11:34AM (#7373486)
True. I think after learning Perl as a second language, I understood Java (my first language) a lot better. OOp in Perl is a bit of hack. Bust it is transparent and you see what is happening, unlike Java, where it is like a black box.
Re:The Mid-Career Crisis of the Perl Programmer by eropple on Monday March 10, 2014 @11:36AM (#7373504)
YMMV, but I found learning C++ to be a lot more valuable for understanding both object-oriented programming as a general topic as well as the JVM and Java specifically.
Re:The Mid-Career Crisis of the Perl Programmer by Natsu on Tuesday March 11, 2014 @12:01AM (#7377349)
Any good Perl programmer should be able to adapt to many other languages.