5 ms·
How to recognise a good programmer
- pius 19y agoThis is good advice. In particular, I've never met a good programmer who treated it as a strictly 9-to-5 thing.
- maurycy 19y agoI'd say that there's a better single indicator of a good programmer. Many other valuable hobbies besides programming. Things like math, economy, philosophy etc.
- jamongkad 19y agoI can't believe he didn't include Ramaze in his #5 list. :-)
- mynameishere 19y ago#7 IBM sends them over and charges 160/hour.
- edw519 19y agoSorry, interesting little article, but I don't buy any of it. A better title would have been, "A List of Some of the Traits That May Correlate with Good Programmers". Would you bet your business on judgements made from this list? I certainly wouldn't. AFAIK, there's only one way to recognize a good progammer (or a good anything else): * * * * * * * DEMONSTRATED PERFORMANCE * * * * * * * Did you do it? On time and under budget? Does it work well? Does it satisfy the stakeholders? How easily is it extended or maintained? <add your own evaluators of demonstrated performance> I also believe that if you can do it once, you can do it again. Evaluating quality by anything other than demonstrated performance is stupid and unfair to everyone involved.
- joshwa 19y agoI think the article is talking about a new-hire situation, not evaluation of one's own employees' efforts. It'd be pretty hard to get metrics like yours in a hiring situation.
- edw519 19y ago"It'd be pretty hard to get metrics like yours in a hiring situation." And who here signed up for easy? In a new hire situation, require examples of work done (on-line or otherwise). Make them code. Give them a conditional mini-project. Get appraisals from former clients, employers, co-workers. etc. etc. etc. I could think of a hundred better ways to evaluate unknown talent that the suggestions from this article.
- Retric 19y agoI might jump though that for a 150k job and or a fairly long 150+$/h project after the interview but IMO an extended interview process is a bad sign. If you can't tell if someone can code in a 2-3 hour interview you're in really bad shape and I probably want to avoid your team and your code. Here are some real questions to separate the coder from the poser. What's the worst hack you have ever done and why did you do it? What's you least favorite language and why? What's the hardest problem you have ever worked on? Why was it hard and how did you solve it? What's the most elegant solution to a problem you have ever devised? IMO: Trick questions and odd syntax issues are just as useless as asking about their IDE of choice or how to solve a trivial problem. PS: If you want to validate my credentials after while we nail down my fee that's one thing, but I am not going to give out references early in the process.
- jkush 19y agoI always ask two questions: What's the coolest hack or project you've ever worked on? and What's the worst hack you've ever committed? I like these questions because if a programmer is good (in my opinion)...you'll see that person light up and get excited.
- eru 19y agoFrom the comments: "I didn't even realised [career programmers] existed! I assumed that all computer science/software engineering etc graduates were previously teenage hackers."
- mov 19y agoContribution to a free software project can be a good indicator too.
- edu 19y agoSo, he will only hire a Ruby programmer? I thinks it's time to proclame: Ruby is the next Blub. Long life to Blub!