9 ms·
The Mid-Career Crisis of the Perl Programmer
- chaostheory 12y ago> tdlr: you should have spent your time learning how to write a CRUD app and a mediocre template system, dependency injection framework, and ORM in Haskell Rails Erlang Scala Rails Python Node Clojure Julia instead of mastering one tool and learning how to solve problems. This is a general rule for everything. The animals that survive are the ones that best adapt (well constantly adapt) to an ever changing environment, since change is the only constant. This is the one major thing I got out of being a computer science major: the language doesn't matter and you shouldn't tie yourself to just one language (i.e. be language agnostic). They drilled into us that we should constantly learn new languages for both fun and profit.
- dima55 12y agoExcept if you keep switching languages, you never truly become proficient in any of them. And you can pry C and Perl from my cold, dead hands. :)
- thirsteh 12y agoLanguages aren't all that different from each other. Most of the knowledge is shared between them (with a few exceptions like imperative vs. functional.)
- dima55 12y agoOh please. A "language" is way more than a way to define functions and add numbers. All modern languages like to rewrite the world: standard library, help system, build system, distribution system, FFI and so on and so on. It'd be great if these were standardized, but language authors love to NIH apparently. Moving to another "language" is a HUGE endeavor, unless of course you like to half-ass it.
- thirsteh 12y agoRight, but there's nothing wrong with being a good programmer who needs to refer to the library docs more often. What's "oh please" is the notion that you can never be good at programming unless you've been using Perl nonstop since 1995. A Python programmer can pick up and become reasonably proficient in Go in a few days, for example.
- Retra 12y agoA lot of this depends on what level of proficiency you're talking about.
- jghn 12y agoSure, but they're not that different, particularly if you've been around the block a bit and seen a bunch of these. For a reasonable definition of the word productive, I've never found it terribly difficult to pick up and be productive in a new language. Sure, a year later I'll look back and say "man, I was so silly back then" but that's not the same as being useless. We routinely hire people at work who don't have experience in our primary language and it's never been an issue. One of the things that irritates me the most about our industry is the fetishization of the difficulty of switching languages. In my younger days people would say that the syntax was too difficult to pick up. Now that people realize that's hogwash they've moved on to saying that the frameworks are too difficult to pick up.
- eropple 12y agoThis isn't true, in my experience. I'm production-comfortable in at least half a dozen languages and yet I've never used any of them for more than maybe a few consecutive months at a time. I can go as deep on the JVM or the CLR as you'd want to go, I won't embarrass myself writing C++ in anger, and in the last year I've gotten quite comfortable with the idea of writing production code in Ruby (which, for me, means diving in and figuring out how MRI ticks). My travels indicate to me that "proficiency" grows from understanding the mental models that go into programming. Within a linguistic family (and most of the languages in heavy use are either dynamically-typed OO or statically-typed OO), the differences are marginal and mostly unimportant. If I had to go write Node ("like Play but without a working type system!") tomorrow--well, I'd quit, but before I did I'd be proficient in a week.
- Retra 12y agoYour experience is very narrow it would seem, and not an example worth generalizing from. So you know Java, C++, C#, and Ruby. That is _not_ a diverse set of languages.
- eropple 12y agoMan, you just read my post and went "I am driven to just be a jerk about this," huh? I'd really like you to tell me how "at least half a dozen languages" translates in your head to "four", because--and I'm not a linguist here, I'm not a dictionary, so maybe I'm wrong but I don't think so--"at least six" and "four" are not equivalent. But since you so nicely invited a brag, I've written code for production use cases in Java, Scala, Groovy, C#, Guile, PHP, JavaScript, Ruby, Python, Perl, VBA, and C. And shell scripting languages, but I don't think--going back to my point--the differences between zsh and bash and csh are really worth getting into. I have not written production code in C++ (aside from the game I'm writing, which isn't yet done), F#, or Erlang, but I know each well enough to look forward to doing so. (I'd need to practice Haskell before getting into it, but I've fooled around with it.) What I did was pick the four closest to the top of my head, folding Scala in with Java because I didn't want to dilute it further. And what I said isn't changed by your desired genital-measuring contest, though I do so hope I measure up; the basic outlines of everything the overwhelming majority of programmers are likely to see in most of their careers are close enough to share a huge amount of proficiency from ecosystem to ecosystem. The principles are so similar as to make the switch from striped to paisley wallpaper just a context switch. EDIT: Oh. I forgot Objective-C. Sorry.
- rtpg 12y agoseeing other languages can help you understand other paradigms better. Canonical example is people learning Haskell or Lisp and then going back to C++ and making much more stateless (and thus more maintanable) code.
- chaostheory 12y ago1. imo Being a specialist in a language and being sufficiently proficient in it are two different things. 2. It's not like you ever let really go of the languages you already learned if you keep using it. 3. It's pretty obvious when a language has run its course. It shows in the job market. Why not transition then instead of staying on the Titanic?
- increment_i 12y agoAs a 'hobbyist' programmer who makes his money outside of the software game, this is something I've really taken note of. And I have to say the programming tech treadmill is one of the most cringe inducing phenomena I've ever witnessed - particularly in scripting languages. Software folks tend to see themselves as futurists in the fast lane, and as a Hacker News-er I tend to carry myself this way as well. But I kid you not, I can't count the amount of articles I've come across where the title is 'X tech is the new ish! - so rockstar lol' and the article is a simple example of http routing or process spawning. It is SO easy to get caught up in this drivel when you're starting out as a programmer. I've since learned to use programming languages to solve problems I care about. If that makes me the forever-novice then I'm cool with that.
- swatow 12y agoSoftware isn't a game, it's an industry. People use particular languages, frameworks, etc. because it makes them more productive. As a professional, I also can't follow every single trend (e.g. I've got no idea what Chef and Puppet are) but I keep an eye on things that are close to my own area, because I don't believe that fads come out of nowhere, or that you can ignore what other people are doing. Most of the major trends I've seen are justified on technological grounds: Node.js - lets you share code between client and server Docker - a more reproducible environment than a VM Python - the most user friendly syntax of any language You have a fake humility in your post, but I would ask you what particular things (e.g. what scripting languages) you think are "cringe inducing".
- increment_i 12y agoTrust me, it's not a fake humility. I really have nothing to do with the development of software in my day to day life. And I wish I could agree with you on the "it's not a game" thing, but having used enterprise Windows software for most of my working life I really can't come to any other conclusion than a lot of the software out there running our day to day lives must be produced in settings not unlike your local McDonald's. Having said that, I've yet to come across a situation where I've shared code between a Node server and client code. Don't get me wrong, I LOVE writing processes in javascript but when I was starting out, the language wars really confused me.
- dogweather 12y agoI can confirm. I worked with Chromatic at the consultancy he mentions; I developed the Python/wx app. He was a stand-up guy, a professional in an environment where most weren't. (It turned out that the company was already having trouble making payroll when they hired me.) The perl dev group's focus on testing was impressive and very forward thinking. But at the same time, the Golden Hammer anti-pattern was evident to me: matching your tool to the client's problems, as opposed to placing the client's problems at the center of your focus. I believe that my CS background helped me take that client- and problem-centered approach. And led me to create several proofs-of-concept in different languages before settling on Python/wx (largely unknown to us) as the best way to meet the project's requirements.
- eropple 12y agoIMO, it's not a CS background that does that. It's empathy, it's putting somebody else's concerns on the level of or even (gasp!) above your own, and that's in pretty short supply around here. Empathy is often confused for cheap populism--because populism is always cheap, I guess--and gets that middlebrow dismissal that's so common in tech.
- chromatic 12y agoIt's both. dogweather had the experience and breadth of skills to explore a range of solutions to find a good fit as well as the empathy to see things from the customer's point of view--not to mention the people skills to make his case so well.
- mrbig4545 12y agothe people who get paid the most are those who can call them experts in the field. you can't do that if you tinker in every field. pick something, work on it, find work doing it and get paid the most. if the work goes away and you need to pick a new field, then what you've learned isn't wasted, you'll still know how to solve problems, just you won't know the idiosyncrasies or the eco system as well as you did. but you can learn that pretty fast. point being, learn one thing and stick at it, that way you'll get more money.
- kephra 12y ago> Do I want to program in Cobol or Mumps for the rest of my life, or even the rest of the afternoon? No. I had been a Perl hacker, and CPAN author (kraehe) ages ago, but time moves on. I learned coding with papertape and punch cards. I wont get any good job, if I would restrict myself to COBOL or Perl. Perl has its strong sides, especially the CPAN culture of testing and documentation is unmatched in any other language. I still use Perl, if there is a module that solves my needs. But my portfolio of languages grows constantly. I dont want to write Perl the rest of my life.
- staunch 12y agoAnyone who has had the experience necessary to master Perl has serious chops as a programmer.
- bane 12y agoLearn to be a "programmer" not a "X programmer". I recently sat down to learn Python a bit. Inside of a week I had useful code up and running. I'm sure it was non-idiomatic and I'll laugh from embarrassment a year from now, but screw it, it works, and real people ship. The last code I wrote before that was in Java. I had to relearn it after a decade of non-use. Real people ship. More recently I wrote some more Python code, it's all hacky and terrible, I can feel it, but you know what, it shipped and has kept a half-dozen people employed for another few months. Real people ship. Most recently I had an issue to solve, not wanting to fight Python's 2.x's stupid typing issues, I hacked it out in Perl. The solution shipped. Real people ship. GSD (get shit done) and move on. It doesn't really much matter what it's written in. It's all bits and bytes, 1s and 0s in the end. Real people ship. (also, don't work for free)
- SwellJoe 12y agoI think chromatic has more than earned the right to call himself a "real programmer". He may not be a real business person...but, he's demonstrably a real programmer.
- gaius 12y agoDomain knowledge trumps language in the real world. It's funny, we mock MBAs who believe they have the generic skill of managing anything, but how many programmers think that they can write programs in any company or industry?
- douche 12y agoOn GSD: You do this for long enough without ever cleaning up after yourself, and you're left with a massive, steaming pile of garbage that you have to then support and maintain. Maybe you're lucky enough to be able to write fire-and-forget code, but in my experience, writing hacky terrible code to ship something just means that I'll have to spend 3-5x time on the phone troubleshooting with a customer, analyzing logfiles and then writing the code the right way in the end, than if I had just done things right to start with.
- vinceguidry 12y ago
- dkarapetyan 12y agoI used to think there was an idiomatic way to write code in a given language, that following conventions and community guidelines was a good thing, that languages had a natural flow to them and writing against the flow was a bad thing. These days I focus on solving problems. Idioms, conventions, languages, etc. are all bullshit. Everything is subservient to solving a problem. Ember or Angular? Don't care. Ruby or Python? Don't care. C# or Java? Don't care. Haskell or F#? Don't care. Statically typed or dynamically typed? Don't care. What is the problem we're solving? Now we're getting somewhere.
- mgkimsal 12y ago"Everything is subservient to solving a problem". Correct. And writing good, clean, idiomatic code usually helps you avoid introducing code-level problems when trying to solve your "real world" problem. You're not wrong so much as perhaps just more experienced to the point where caring about the idioms isn't much of an issue any more, not because idioms don't matter, but because you're writing code that's good enough. i've found the 'standards' and 'idiomatic code' to be useful not so much as a benchmark for "you're 100% wrong if you don't do this" but "you're creating another set of problems for yourself if you're not careful". "Ember or Angular? Don't care. Ruby or Python? Don't care. C# or Java? Don't care" Well... you may need to care, because one of the problems you may have to consider is long-term maintenance as well. Using Ruby for "project X" in a team of 15 .net developers with extensive C# experience, simply because "Ruby is best for this problem" is probably just trading one problem for another.
- vinceguidry 12y ago> Well... you may need to care, because one of the problems you may have to consider is long-term maintenance as well. Using Ruby for "project X" in a team of 15 .net developers with extensive C# experience, simply because "Ruby is best for this problem" is probably just trading one problem for another. I'd like to reiterate this point. At some point, somewhere down the road, a different programmer than you is going to have to read your code and try to figure out what it does. If you don't learn your languages well enough to be idiomatic, then you'll be contributing to technical debt load instead of helping to pay it off. Unless you're doing big enterprise consulting. That's an entirely different sport.
- swatow 12y agodisclaimer: I've never written a line of Perl. When I look at the programming world, my primary instinct is that if something is popular, then there must be something good about it. Take JavaScript. In spite of its limitations as a language (the worst of which is not having a canonical OOP style) there is no easier way to create a single GUI for 3 platforms, as JS. I could make similar comments about Python and C++. I don't really understand the point of view that using [old language] is an indication of really knowing how to program. Apart from some minor details, all imperative and OOP languages are fundamentally the same.
- dkarapetyan 12y agoWhy do you say that if something is popular then there is something good about it? The world is full of sub-optimal solutions to all sorts of problems. This is especially true for programming languages and frameworks.
- swatow 12y agoIt's just my own view that I developed based on everything I've experienced. It can't be boiled down to a single assumption, or a single piece of empirical evidence. I studied economics so I'm very influenced by economic theory. But on the other hand so called "network effects" do imply that suboptimal technologies can become dominant. In practice, I don't think that languages usually become dominant purely by network effects. They need to have a real advantage. To take a concrete example, Python has very user friendly syntax. This allows people to quickly iterate on code. Another advantage of Python is its complete standard library, and availability of other libraries. But these things probably would not have existed if Python was not such an efficient language to program in.
- mercurial 12y agoTo take another concrete example, PHP is extremely popular. It doesn't mean PHP-the-language is better than less popular alternatives, it means it's extremely easy to throw things together and deploy (mostly due to almost universal support on VPS). Nonetheless, PHP's history is an accumulation of appalling technical decisions and security holes.
- toadi 12y agoActually the company I founded start 2000 and was quite succesful used perl. Off course I wrote the MVP in it. I loved perl. When I sold it due to personal reasons I was not yet ready to retire. In that time and especially in Europe buy-outs were quite modest. I started doing consultancy until I would have a new idea and start working on that one. Indeed the golden cage of consulting can be dangerous. I'm already consulting 5 years and didn't start anything new. I don't consult as a programmer anymore. I implemented Agile in my own company and now I'm an agile coach in large enterprises. Programming I still do in my freetime just to keep me sharp. But here in Belgium 99% of the projects are CRUD projects so I'm not really missing out on anything. Most of the times senior developers go to architect roles not because they want to stop coding but because they're tired of writing CRUD code.
- zura 12y agoI don't know, I guess it requires a different mindset/discipline. I can't imagine myself happy doing agile coaching. Here in Georgia 99.999% of projects are CRUD, that's one of the reason I work remotely for more than 8 years now. Mostly, C++ related work.
- allendoerfer 12y agoI do not want to sound to harsh here, but seriously you are requesting a bit much. Judging by your choices of words, you realize it yourself ("special snowflake"). The system works a certain way, you do not want that, fair enough. You then continue how you do not want that consulting thing either. So you go back and basically say, that you want to be hired by a company, which produces a product of your interest. They should use a technology that does not advance while there are other choices, which would lure in coworkers, who are interested in using it. It does not matter whether Perl is technically a reasonable choice. There are other more important metrics for a company. When you get hired as a programmer you got to program. If you want to make bigger choices, stay your own boss. I get, that it is hard to move on from a beloved community and something that defines yourself. But really, I do not think, that Lua, Ruby, Python - you name it - or even PHP are so different, that you could not use some of those 20.000 hours of experience productively in them. Also, you can go back to Perl anytime. I think you wrote that rant, because you were faced with making a decision and wanted to wallow in memories of the good old times. I hat this once on a much smaller scale when I switched from PHP to Python. As many people already suggested: Identify yourself as a programmer not a Perl programmer. You will highly increase the likelihood of getting into an environment that satisfies you when language choices is not important to you anymore.
- andsmi2 12y ago+1 for reminding me about mumps.
- jkot 12y agoThere are money to be made in Perl, but mostly on old code maintenance.
- pre_action 12y agos/Perl/software development/
- crpatino 12y agoI am biding my time and waiting for the 2038 bug to come along. The cool kids of that age will probably never have seen a compiler (any compiler) before, and I am going to line my pockets like it's 1999. ;)
- brudgers 12y agoNext time there's a "How do I freelance?" Ask HN, please use this; If you find a good client, you treat him or her like a combination of the Pope, the Queen, and the Dalai Lama, because a trustworthy client who pays you on time and doesn't argue over little details of the contract is better than gold.
- mooreds 12y agoThat happened to me. The client was so good that I became an employee!
- zzzcpan 12y agoNot much changed over the years. Chromatic is still praising Moose and other bad ways to code. > Moose is probably the singular reason there are any significant new projects in Perl in 2014. There is another side of that story: Moose is probably one of the things that contributed to Perl's decline, along with modern Perl, Perl 6 and overall focus on all the wrong things. Anyways, I wouldn't take chromatic's words too seriously. Learn Go guys :)
- pmoriarty 12y agoWhat's wrong with Moose, modern Perl, and Perl 6? What makes them "the wrong things"? How did they contribute to Perl's decline? What are "the right things"? What should the Perl community have focused on? To me it seemed like a bunch of Python and Ruby fans came out of the blue and started endlessly chanting "Perl sucks", or "Perl is line noise", and that apparently was enough to turn a lot of people away from Perl and on to the newcomers. Sadly, these chants often came from and were directed at people who'd never used Perl themselves, or didn't know much about it at all. So it was really a case of the blind talking to the blind. Not that I love Perl. It's got some warts. But so do Ruby and Python, and every time I try to pick either of them up, I notice a ton of things that are as bad or worse than Perl. And that just makes me sigh.
- zzzcpan 12y ago> To me it seemed like a bunch of Python and Ruby fans came out of the blue and started endlessly chanting "Perl sucks" I think that was a side effect of experienced Perl developers publicly explaining why Perl was not that good and why they chose another language. Others respected their authority and started repeating and so on. So, the bigger problem was: experienced developers were fed up with Perl for various reasons and started to speak up. And they were not wrong. Many years ago there was a perl compiler, but at the time when everyone was moving towards virtualization and ease of deployment was particularly important - it got abandoned. Performance and memory consumption were never considered as problematic either, but they always were. Even simple log processing was not viable for anything, but personal homepage sized logs. It was very disappointing for many people. As for Moose, etc., Perl had a perfectly good object system. Everyone knew how to bless a reference and make it into an object. It was hard to abuse it, nobody encouraged OOP, things were good and manageable. And yet, community decided to go farther into OOP, promote Moose, promote new syntax features, promote new ways to build modules. Things got messy in the process. Perl still didn't address any real problems, but it was a pretty much new language and a burden on everyone. Suddenly people found themselves in a position, where they needed to decide of whether they want to learn all the new things in Perl or not and learn some other language instead. > But so do Ruby and Python, and every time I try to pick either of them up, I notice a ton of things that are as bad or worse than Perl. I don't see them as alternatives to Perl. I think they are in decline too.
- michaelochurch 12y agoTo me, this isn't really about Perl. It's about the multifurcation of programming in general. We have ourselves a shitty industry, and whether you're in-house or a consultant, you engage with its nastiness and aggressive anti-intellectualism on a regular basis. It's hard to get the good consulting jobs without establishing yourself as a specialist. Clients don't want a smart generalist who'd like to try herself out with machine learning; they want the 20-year expert (and for only $120 per hour!) But, if you specialize and get unlucky (and a lot of it is luck, because factors other than quality influence which tools win and which don't) you end up having loaded up on skills that no one needs. At the top levels of talent, the people who are actually able to evaluate it have better things to do than to judge others. So you need credentials, blurbs on the CV, credibility, etc. ...you're not dealing with VCs who underpay you and dangle ever more diluted RSUs in front of you for that 1% chance of an acquihire payout that'll slightly pay more than if they'd paid you a market rate for the start... Here's why the VCs and career executives won. They spent as much time getting good at office politics as we did at Perl or Haskell or Clojure or machine learning or computer vision. The difference is that office politics is a transferrable skill. The stuff we learn is much more powerful at advancing the state of society, but if the industry turns against us, that time is "wasted" from an economic standpoint. It's not actually wasted; it has still made us better at our jobs, but it doesn't make us better on paper, which is what matters if you're a consultant in a rough economy who needs to eat. Eventually, the VC model will break. What's interesting about it is that the numbers (in funding amounts) appear large, but the expectations mount so fast that these companies are actually being run on a shoestring budget (relative to what's expected by Year X, and because the rapid-growth expectations pretty much mandate a next round of funding rather than a stable let's-get-some-revenue strategy). A $5 million investment seems like more than you'd need, until you realize that you're going to need 25 more people to appease your investor-boss and that's going to put you in front of investors again, depriving you of the time or freedom to do anything else (like build a business, maybe?) in about a year. How do you keep programming fresh? That's a hard one, because humans tend to create pyramidal structures and what that means is that there are fewer positions for 10-year programmers than fresh grunts who are still excited by the CRUD projects, and at 20 years... you're either doing R&D in an AI research lab usually with a "Fellow" title that is VP-equivalent and therefore gives you a right to be old... or you've moved into a management role... or you've missed at least one boat. At 7 years, you've learned everything general you need to know for 99% of corporate programming. Sure, there's the treadmill of new frameworks and new dresses on old concepts, but you're pretty much maxed out unless you can convince business types that you're something other than "just a programmer"-- perhaps a machine learning expert or "data scientist", perhaps an architect, perhaps a Dir/VP-equivalent elite programmer ("Principal" or "Distinguished" or "Fellow") who has the clout to work on what he wants, perhaps a manager, perhaps a founder. The good news is that, for most of us, it's not actually that hard to do. Not all "business types" are morons, and many are good at what they do and make your life easier-- if you can convince them that you're a cut above the commodity programmers who "deserve" to be corporate subordinates. The problem is that, while learning office politics is a lot easier than plenty of technical things that we gladly learn just for the challenge, it is a huge distraction, and those lessons often come at random when you'd rather be learning other things. If you expect a 40-year career working only on hard technical problems, you're not going to get one, because the days of Bell Labs are over and, anyway, modern academia is far more political than most corporate jobs. You're going to have to learn the politics of business, because (channeling Trotsky) you may not be interested in political fights, but they are interested in you.
- jqm 12y agoI'm sure there is good perl and good perl programmers. But, having spent a portion of the last several months going through 3000+ line perl scripts written by a person with no formal training who had figured out just enough to hack something together but not enough to efficiently use functions, nor to maintain the code they wrote, I'm feeling less then sympathetic with the OP and perl in general....