11 ms·
> 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 Rail
by 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.