The part about "team player" doesn't make much sense to me.<p>How do you decide if someone is an "average team player" or an "above average team player"? Hard overall, impossible from a LinkedIn profile. Unless of course, they base their decision from what the people have entered themselves. But then again, who would put "I'm an average team player"?<p>That being said, considering the similar setup for comparison, it's interesting that "good communication skills" rates so poorly comparatively to "team player". It's not completely surprising I guess for software development (though I might disagree), but it also means I might want to update my profile/resume…<p>On another note, even though I rarely take part in the "programmer/developer/engineer" discussions, I find the "Python/PHP/Java… engineer" titles to be odd. These people are probably "software engineers", but "Python/PHP/Java… developers". The specific language doesn't mean much to your ability to engineer software. (unless maybe, you actually work on the language itself)
Based on these figures: do NOT learn Ruby. Ruby is dead last in the "face-off", and looks like it would put you at a <i>significant</i> disadvantage compared to Java or Python.<p>That makes me wonder about two things:<p>1. Is Mixtent wrong?<p>2. Do companies really see Ruby on a resume and say "nope! next?"
What is this bullshit? Looking for a job? Convince me you know what you're talking about. Show me something I didn't know and convince me it's worth knowing. Demonstrate you know big 'O' notation (and maybe tell me how little 'o' and \omega are different). Draw me a binary search tree. Show me how a skip list works. Fill in a multithreaded producer / consumer skeleton and get it correct, then make it fast. Explain how UTF-8 works from first principles (i.e. what's wrong with ASCII? How would you fix it? Now how do you optimise the answer?)<p>I don't give a crap if you know $TRENDY_WEB_LANG. We don't write anything in either Python or Ruby, and likely never will.
Am I the only one who thinks it's terrible that companies are apparently defining engineers based on languages? I know Python AND Ruby, would that make their heads explode?
I'll post this for the new HN members, since I would've loved to hear this after joining: the companies you want to work for don't give a damn about what languages you know.<p>You want a job? Learn how a splay tree performs better than a binary search tree, and what that says about worst-case algorithmic complexity. Grok the difference between training versus inference, and how a well-trained model can completely fail in practice. Learn how programming can be functional, imperative, or logic-based, and then mess around with Haskell, C, and Prolog. Then use Python to see how all three can blend into one dialect (okay maybe not logic-based).<p>Good companies don't look for languages on your resume--they want people who know their stuff. List comprehensions or decorators don't matter--you have to demonstrate an ability to learn <i>anything</i>, whether it's syntactic sugar or obscure data structures with specific use cases.
I don't know what to make of this. I see no actual data (or even a link to it). I don't know if they corrected for other variables and having "python" on your LI profile is predictive or just correlative.<p>I think I have actually lost knowledge instead of gaining it after reading this infographic.
Is it just me or is the text really, really hard to read? Maybe just today I've finally gotten really old, but please: don't do that. If you <i>have</i> to write your text in a graphic, at least make it easily viewable.
I think it says:<p>"learn Python, win over your peers".<p>"don't be a dick, win over your peers".<p>"learn ruby, convince your peers you're good at CSS too."<p>"work at facebook/google and be popular."<p>Mixtent is a popularity contest. My bet is, if you asked someone on the street with no knowledge of programming "who is a better engineer". Split by name it would be random 50/50. But if you included where they worked, then the Facebook or Google person would win.<p>It is interesting though.
Interesting information. I am curious if they can tell whether this will be the same over time or if things such as Node.js and other languages will take over.<p>I figure being a team player will probably never change.
Ruby is actually incredibly beautiful. I used to think Python was beautifully concise and minimalist till I started playing with Ruby.<p>I don't use Rails, though. But I do write and use Ruby for hundreds of everyday data and text manipulation tasks. Its also great fun for sucking data from a database and slicing and dicing it into a dozen different formats really quickly.<p>I love its natural language constructs. They're incredibly productive.<p>Python is like that, too but I find myself drawn to Ruby. It <i>is</i> fun in itself and it <i>does</i> make drudge-programming fun again.