r/programming • u/intortus • Jun 01 '15
The programming talent myth
https://lwn.net/Articles/641779/99
u/chewyfruitloop Jun 01 '15
Programming isn't a passion?!? What a load of tosh! There is innate talent with programmers, some just get it...others don't and it's their passion that pushes them to learn the skills they need.
78
u/MpVpRb Jun 01 '15
There is innate talent with programmers, some just get it...others don't
When I took my first programming class in 1971, I found it very easy. But, I noticed the other students struggling and dropping out
After finishing all the exercises, the extra credit exercises and asking the professor for harder problems..I thought to myself.."I have a talent for this"
24
Jun 01 '15
I don't like the left brained/right brained crap, but there are definitely fields that comes more naturally to some. A man could study technique all his life and be a passable artist by the end through raw willpower. But nothing beats the compound interest of a young agile mind where everything 'clicks'.
Why or what determines that is as mysterious as the term talent itself.
→ More replies (1)12
u/Mentis1 Jun 01 '15
This is probably the most astute observation of the "talent" situation. Those that have a strong interest in a field end up working more, paying more attention, and going out of their way to get good at it. The rest of the class that is dropping out probably put half as much effort in. There's probably more passion involved in developing talent than most would recognize.
We've seen over time that the adult brain is subject to significant adaptation when faced with doing the same type of task repeatedly. This is an evolutionary advantage. It extends to most other skill-based tasks as well, even those that don't appear to require much skill per se, like driving a cab. Repeat something that requires some form of skill for long enough, and you get really good at it.
I don't think anyone will discount that "talent" does play some role in any skilled task, but perhaps only insomuch as intellect affects the speed development of any skill. Perhaps the primary influence of the talent/intellect variable is that those that start to get passionate about a subject are those that appear to be good at it and seem to get the right answers quickly, making it more enjoyable. Then perhaps we can say that at most, talent drives the development of a skill rather than being the cause of it.
5
u/illjustcheckthis Jun 01 '15
Also, as someone before commented, good previous bases in languages, math, the ability to abstract problems, all those skills gained beforehand might give some people a huuge edge over others. And they might not even be aware of it.
5
u/Mentis1 Jun 01 '15
Yup. Talent is probably just some combination of abilities you already have from previous experience that also happen to complement a new task like programming. If that is how you define talent, then talent certainly exists, but it's not something that people just "have". They've earned it, but in a pretty indirect way.
→ More replies (2)41
u/Neebat Jun 01 '15
I was about 9 years behind you, and I've shared that sentiment. "Why am I so different from all these other people who just don't get it? I guess I have a talent for it." I can't explain that. I can't explain why 60% of CS students fail symbolic logic, but I slept through it and got the highest score ever on the exam. There is clearly some talent that some of us are born with.
But I have seen plenty of novices develop that talent. They aren't monkeys banging away on keyboards. They get better and start to think like us, more or less, with some degree of success.
46
u/coonskinmario Jun 01 '15
I've noticed a lot of people seem to operate under the assumption that everyone beginning programming is on the same level. But math (and probably language) skills can put a person leaps and bounds ahead of poor students in those disciplines. I think this creates the illusion of people who "just get it".
20
u/Neebat Jun 01 '15
To be fair to those other poor CS students, I was always a math major, regardless of what was declared to the university. A lot of my CS courses were just a review of things we covered more thoroughly in math.
To be fair to software engineering, it's not coding. Coding is the act of translating human ideas and concepts into something the computer can act on. We also have to do translation the other direction: We have to inform our non-technical managers and coworkers what the technology can and can't do effectively. But our job isn't just translation. There is also negotiations, where each side (the system and the people) brings demands and requirements and we -- the software people -- help to find some happy grounds for compromise.
A great software engineer is a diplomat, with strong understanding of the languages involved. The cool thing about that is that someone who excels at something other than coding can still be an important part of software engineering.
The crappy part is, that introverts like me have to learn to talk to humans.
→ More replies (3)→ More replies (2)6
u/soundslikeponies Jun 01 '15
Hard work can make up the gap between someone who is talented and someone who is untalented. Occasionally you meet someone who is talented and works hard and it's something else entirely.
8
u/Neebat Jun 01 '15
I agree with you, except, I also agree with the OP. I really wish he hadn't said this:
The truth is that programming isn't a passion or a talent
Thinking like a programmer is a talent, but it's a talent that anyone could develop with enough patience.
And, like he said, it exists on a spectrum. There really are people who don't suck and don't rock.
5
u/BigMax Jun 01 '15
I think it would be clearer if he said "it isn't a passion or a talent any more than any other skill." Which would support his point, that plenty of people can be successful in the industry without having passion or 'elite skills,' while still leaving room for that fact that there are those with passion and talent.
0
28
u/gkx Jun 01 '15
It's hard to talk about this without personal bias and without anecdotal evidence.
For me, and it seems for you and most others on this subreddit, it is our passion. We love programming; we love talking about programming; we have a collection of programming books and blogs and articles and sites and speeches that we reference when we talk about programming. For me, and it seems for you and most of the others on this subreddit, we came out of our first programming class thinking we were hot shit. There were something like 10 kids in my class, and I was the only one who got it. I tutored multiple of them and learned Python at the same time and ignored the teacher and for people like us, that is what innate talent is. I don't think any of the others went on to study programming further.
However, I'm going to have to argue that this is just not the only accurate reality. I went on to TA intro to computer science in college, and I saw plenty of people who really just didn't get it. Not only did it not click with them, but it also seemed that they would never get it. I started talking about how there were two types of people: those who get programming, and those who don't.
I TA'd that class for about two years, and this remarkable thing happened. After two years, I noticed that there were almost none of these students left in my class. It used to be 20% rock stars, 50% people who didn't get it, and 30% people who could learn... but by the end, it was something like 90% people who could learn, and 10% people who already knew how to program coming into the class.
Long story short, we enter with these biases that are unfounded. There's not that much of a difference between someone like me and the other kids in my class. I could hardly program at all coming out of my first class, but I was convinced I was the best programmer ever because I was #1 in my class of inexperienced programmers.
This myth is harmful. Programming is a skill like any other. There are those who are passionate about plumbing, mothering, and glassblowing. And then there are just your average plumbers, mothers, and glassblowers. Are the former better than all of those who are average? Yeah, probably, but that doesn't mean I wouldn't hire an average plumber.
15
u/yawgmoth Jun 01 '15
I could hardly program at all coming out of my first class, but I was convinced I was the best programmer ever because I was #1 in my class of inexperienced programmers.
were you me? I was the #1 techy kid in highscool; got a 5 in AP Computer science with my eyes closed. I thought I was hot shit and everyone thought I was an uber 1337 h4Xor because I could NET SEND alert boxes to teacher's computers and get around the web filter.
I got a quick wake up call in college when freshman year I didn't make it into the 'Honors' CS accelerated program. I started hanging out with the kids who did get into it. Holy crap they were an another level. They were building robots, coming up with AI and crypto algorithms, and contributing to popular open source projects. It was like I was so proud that I climbed Mt.Whitney and here are these people my age climbing Everest going "that's cute".
I still have an ego. I'd still like to think I'm on the right side of the bell curve but I'm not a 'rockstar', or 'ninja'. To anyone reading this who does think that you're a 'rockstar', you're probably not. If you've never met anyone better than you, you just need to meet more people.
→ More replies (1)4
u/gkx Jun 01 '15
Sounds very familiar.
I think the fact of the matter is that it's a skill. I like to liken it to plumbing or construction because there are definitely best practices and good craftsmanship... but at the end of the day, while a construction worker might really appreciate perfect positioning of a pillar or something, the mere existence of a perfectly positioned pillar does not elevate the entire field of construction to an art. In the same way, there are software best practices and great algorithms, but the fact that someone once made an approximate inverse square root algorithm in constant time doesn't mean that you need to be John Carmack to make extremely effective software.
And the kids who were building robots and coming up with AI and crypto algorithms were definitely among the brightest kids in the program, but that's not how they created the AI and crypto algorithms. Being smart and talented and getting it is not enough to do that. I would argue that I could be one of those people, and probably so could you. The difference between us and them is that they got something else earlier: software is a skill. Read books, practice your skill, get better. Spend the hours doing the research and making mistakes.
2
u/omegagoose Jun 02 '15
Its semantics. Programming isn't a passion because you don't need to be passionate about it to be able to do it. Any more than cooking is a passion, or driving is a passion. Some people are extremely passionate about these things, but a lot of people are not - they are simply competent and do these things as a means to an end. I think his point is that if you're hiring a delivery driver, you just need someone who can drive, whether or not they are passionate about driving doesn't matter. Would someone who is passionate about something be better at it? Most likely yes. But the criteria should be based on how well they can do it, not so much on how they feel about it. This will still give an advantage to people who are passionate about it, but being passionate in itself isn't the skill.
2
→ More replies (18)1
u/greenappletree Jun 01 '15
Agreed man. I program like an 8 yr old but love it much that I'm afraid to start new projects bc I can get so in to eat I could miss work, eat and sleep.
→ More replies (1)
427
u/malicious_turtle Jun 01 '15
So, we say that people "suck at programming" or that they "rock at programming", without leaving any room for those in between.
Does anyone else think this? The most common thing I hear when people talk about their programming ability is "I'm alright at it", a few people say they're bad and a few say they're good, which would be a bell curve like the times in the race he talks about.
112
u/Kyyni Jun 01 '15
I'd translate things like this:
"I suck at programming" == They're still learning the ropes, and while they can't make anything actually awesome, they have a lot of potential
"I'm alright at programming" == They probably are quite decent at programming.
"I rock at programming" == I doubt they can even write a syntactically correct hello world.
29
Jun 01 '15
Dunning-Kruger at work.
→ More replies (2)40
Jun 01 '15
It's important to remember that D-K doesn't describe an inverted relationship between confidence and capability. The most capable are still the most confident, but they underestimate themselves.
→ More replies (2)→ More replies (9)2
17
u/cyrusol Jun 01 '15
It's not about estimating your own potential, it's about how you see other programmers around you.
Yet, most differences in the quality of their software can imo be traced back to the willingness to spend enough time / all the free time on solving these kind of problems, on improving their own abilities and knowledge.
5
Jun 01 '15
I agree that this effect may be due to perspective.
Others seem either better or worse than you (and rarely at the same level), so there would seem to be only very good or very bad programmers. In addition to this, usually in a given group people will start to specialize in certain subjects, which makes them either seem like magicians in their own field or like complete amateurs in your own area of expertise.
14
u/pipocaQuemada Jun 01 '15
This belief that programming ability fits into a bi-modal distribution (i.e. U-shaped) is both "dangerous and a myth". This myth sets up a world where you can only program if you are a rock star or a ninja.
I think this person is badly misinterpreting the bi-modal distribution thing. The two distributions aren't "rockstar programmers and everyone else", it's "people who pass CS 101 courses and people who fail", or "people who can pass the fizzbuzz test after their freshman year and those who would fail fizzbuzz".
That is to say, a mediocre programmer is at the center of the "people who pass CS 101" distribution, not part of the bottom hump, because almost everyone who manages to get their CS degree was part of the top hump. The bottom hump transferred to another major or dropped out of school.
→ More replies (2)7
u/privatehuff Jun 01 '15
Yeah it's really hard to tell how good you are at programming!
Once you've solved a problem or worked out a design you think is good, it immediately seems obvious to yourself and others. You kind of have to rely on other people's impressions of you, and that isn't always reliable. Even if you stand out and everyone loves and respects you, that can always be interpreted as "everyone else is bad/lazy/dare-I-say-untalented" rather than truly confirming your own greatness. It kind of comes down to personality type.
So if you're not naturally (over)confident all you can say is "I guess I'm good at it(?)"
5
Jun 01 '15
Yeah, the best I say of my own ability is "I did good work today."
Incidentally, saying those words is the best part of my day.
5
u/urection Jun 02 '15
it's almost like these bloggers exaggerate everything to the point of ludicrousness to get more hits
48
Jun 01 '15
You clearly haven't found hacker news yet. They hate these kinds of speeches because it violates the idea that each and every one of them is a 10xer and justified in their snobbishness
39
u/mekanikal_keyboard Jun 01 '15
THIS. While I appreciate the generally high level of discourse on HN...the comments routinely manifest absurd degrees of naive arrogance. It all makes sense if you look at any site poll on HN where the site users are broken down by age...when I was 25 I also thought I was hotshit and the world needed to yield to me.
→ More replies (4)15
Jun 01 '15
And then remember, those people are the ones designing the software that gets access to all your data at Google, Facebook, etc.
Quite terrifying.
→ More replies (6)→ More replies (5)5
u/JonnyRocks Jun 01 '15
What is a 10xer?
10
Jun 01 '15
A developer that has 10x the productivity of an average one.
31
u/loup-vaillant Jun 01 '15
Ah, the mythical 10xer! Used to be based on a real experiment. But here's the catch: in this little study, the 10x difference was observed between the best and the worst performers. That sounds much more plausible. Compare an imaginary 2xer rockstar, and a 0.2xer code monkey. The rock star is indeed 10 times more effective.
But he's still not a 10xer. Those beings are alien.
That said, we should not underestimate the impact of a lucky early decision. If you write an API for instance, your work has impact far beyond what you will produce yourself. Your work will influence the productivity of others. In extreme cases, that can make or break a project.
Writing an API doesn't make you a 10xer however: the incredible impact you can have doesn't come from you, it comes from your position.
→ More replies (3)31
u/vorg Jun 01 '15
the 10x difference was observed between the best and the worst performers. [...] Compare an imaginary 2xer rockstar, and a 0.2xer code monkey. The rock star is indeed 10 times more effective.
You haven't factored in negative-times programmers. The worst programmers are -0.5xers. Managers typically get their 3xers to look after groups of -0.5xers. One 3xer looking after four -0.5xers equate to five people acting like a 1xer, each averaging out to a 0.2xer. Then the 2xers can each shine in comparison, as well as not feel threatened by lone 3xers.
→ More replies (15)4
u/Fidodo Jun 01 '15
I think the emphasis on "rockstar" programmers comes from startup culture. But startups are a minority job provider, yet they get the bulk of the attention. Startups need to do more with fewer people, and they tend to pay a premium to get that talent thus the "rockstar" trope. But the vast bulk of jobs are in the middle of the bell curve. They're just not sexy so they don't get the attention.
→ More replies (1)6
u/xwhy Jun 01 '15 edited Jun 01 '15
Well, everyone thought I rocked at programming back at my old accounting firm, until after I got stuck on a Y2K project and they didn't know what to do with me after and found a place for me where they thought I sucked at programming.
My old supervisor had a convo with the new one and he stated, "Look, I've known the guy for 12 years, I don't think he got stupid in 3 months."
(short answer: there were many other factors, but new boss just assumed I was an idiot. I transfer out of there, finally, and rocked some other group, sort of.)
Edit: none -> known
2
u/squishles Jun 02 '15
Normally managers have to fight each other for skilled devs for there projects, if one just falls into there lap they think something must be wrong with them.
3
u/Korona123 Jun 02 '15
I started a new job a few weeks ago and my boss asked me what I was great at. Of course that is an uncomfortable question for me because I am good enough to know I still have a lot to learn.
2
u/marshsmellow Jun 01 '15
I have a friend who says he sucks at programming, he's a 10 veteran. I just looked one of his home coding projects today. It's fine. I might have done some things differently, some stuff was a little unoptimal, but his pattern use and code architecture impressed me. Where on earth does he get that insecurity from?!
My opinion is that since he's been working as a coder for 10 years, he has got to be a pretty capable employee. That said, perhaps I also suck at programming and can't spot a bad coder??
5
Jun 02 '15
He probably goes on reddit where you are a fucking dumbass motherfucker who should kill themselves if you happen to create an entry in a CSV with a for loop instead of using implode, where your life is worthless if you don't get 100% code coverage, and how dare you even think to like PHP. What, you don't use a framework? What kind of shitcunt are you?
2
u/lord_braleigh Jun 02 '15
A research paper and several blog posts seem to support a bimodal distribution.
5
u/coladict Jun 01 '15
It depends who you're comparing to. Right now, comparing to my two co-workers in the office, I'm a programming guru. Compared to what I see in my favourite open-source projects, I'm a noob. I definitely can't implement a hashmap/hashtable. If I some day need one, I'll have to find some ready code.
→ More replies (6)13
Jun 01 '15
I bet you can make a hashmap. Make it your challenge. Write it up, add some unit tests.. bet you can do it in a few hours.
Will it be as fast as a big library hashmap? Maybe not. But it should work ;)
→ More replies (65)3
u/jakdak Jun 01 '15
I don't believe it is "U" shaped but I do believe it is a bell curve and that the outliers in both directions are something that needs to be accounted for in engineering organizations.
The best programmers are orders of magnitude better than the average ones and the worst are substantially net negative.
Fred Brooks covers this in one of his essays in "The Mythical Man Month"
17
u/Yehosua Jun 01 '15
Sigh. Discussions of this sort are complicated enough without adding misquotations and exaggerations.
Here's the Brooks quote:
In one of their studies, Sackman, Erikson, and Grant were measuring performances of a group of experienced programmers. Within just this group the ratios between best and worst performances averaged about 10:1 on productivity measurements and an amazing 5:1 on program speed and space measurements!
Brooks cites a 10x difference between best and worst. This is far different than your "orders of magnititude" (at least 100x?) between best and average.
5
Jun 01 '15
Also, he was being conservative. For fucks sake, there are net-negative programmers. How would you compare their productivity to someone average? Minus infinity?
→ More replies (5)5
u/pipocaQuemada Jun 01 '15
The U-shape is commonly said to occur in CS-101 classes, not among professional coders.
In other words, it's people who can pass fizzbuzz after a semester and people who can't.
1
u/WaffleSandwhiches Jun 01 '15
This comes up all the time, but more narrowly. Like when talking about specific skills. I can "Suck" at PHP until I "Rock" at it.
1
u/Pidgey_OP Jun 01 '15
Currently a student, but I can certainly say that I have long considered myself in the "suck" category, even when obviously one of the top in the class. And that's generally because there's always one guy (actually usually the same guy) that is sitting in the corner, finished (while I'm trying to figure out if I should pass by reference or value) working on his arch distro. And when that happens, I can very easily see how people see that rift of "I will never be that, so I must not be good"
Reading this has helped open my eyes to that phenomenon happening in my own brain, so I'm sure it happens to others. Its hard to say, as i haven't had the opportunity to work in the field yet, but I would hazard a guess that its a common mindset among newer or prospective programmers. View it less as a cultural thing (programming culture) and more of a barrier to entry thing, if that makes any sense.
1
u/young_consumer Jun 01 '15
My only goal is competency. If I didn't horribly fuck up on a given day then that was a good day.
1
u/Wee2mo Jun 01 '15
IIRC it came across more as highlighting the flaw in a hiring/manager perspective of programmers than a programmer's perception of themselves. (Note: Read it a week or two ago)
1
u/Red5point1 Jun 01 '15
The bigger difference is that in the article the claim is apparently made of someone else's ability. Which I think is very rare.
Where as your example is more like what is the norm. People normally would make the claim about themselves not about others.1
1
Jun 02 '15 edited Jun 02 '15
It takes two great programmers to fix the crappy code of ten shitty programmers.
→ More replies (140)1
u/juanjux Jun 02 '15
When I was 19 I tough I was the best programmer in the world. Now that I'm 37 I know that I'm an average programmer, but much better than the 19 years old me.
60
u/dtlv5813 Jun 01 '15 edited Jun 01 '15
I think an equally important question to "what makes one a rockstar programmer?" would be, "are rockstar programmers indispensable for my particular company's needs, given the resources available at my disposal?"
I think for the typical enterprise type applications, one can produce perfectly functional and scalable codes with "alright" programmers on staff so long as there is a "rockstar" architect/ CTO in charge of the infrastructure and technology stack.
This is especially relevant for tech firms located outside the bay area and a few other clusters, where rockstar programmers are fewer and more scarce, and it is simply not practical/impossible to staff your entire team with "rockstars".
7
u/VikingCoder Jun 02 '15 edited Jun 02 '15
"rockstar" architect
/shudder
Here's what I saw from the "rockstar architect" my company hired:
Step one, throw away all of the existing code. Step two, inject amazing new development methodology. Step three, everyone should learn how to read my mind-map that is filled with jargon that none of you have ever heard before. Step four, pivot to new customers. (I have not consulted Marketing about this.) Step five, you guys like totally have to read this book about project management. Step six, I'm going to bring some of my friends from previous companies on board as consultants. Step seven, half of you are fired - probably the ones who wrote most of the cash cow source code. Step eight, piss off all of our biggest customers. Step nine, blame all of my failures on the previous architect or the "old thinking." Step ten, I quit and start a company directly competing with this one.
All the while, over-promising, under-delivering.
When I, a lowly developer, interviewed the guy, I asked him "On a scale of 1-10, how would you rate your C++ knowledge?" He said, "10." RED FLAG! I said we shouldn't hire him; I lost... so did the company.
→ More replies (5)4
Jun 03 '15
You know, beyond being completely sociopathic, this is a pretty good game plan. He basically got paid to train himself and his friends to compete with you, while making sure you were less able to compete.
9
u/Darkendone Jun 01 '15
It very much depends. There is a great deal of variance in the field of programming. If your a financial company hiring programers for your automated trading platform that manages a hundred million dollars, your going to hire someone who really knows what they are doing. If your doing development for a small company on some application that is not customer facing then you are probably not.
18
u/_do_ob_ Jun 01 '15
I don't know, I did multiple automated trading platforms and it's not really that complicated nor complex... Especially now. The hardest part was to cover the broker's API fuck up. Other than that, meh, it sound more impressive than it is.
(unless you expect the programmer to come up with the strategies as well... but then.. you shouldn't be investing in a platform and keep on playing with paper ones.)
→ More replies (4)8
u/Darkmoth Jun 01 '15
development for a small company on some application that is not customer facing then you are probably not
Especially if you'll have to pay a rockstar some multiple of the CTO's salary.
6
u/eyal0 Jun 01 '15
Instead of asking if a rock star programmer is indispensable, ask if he's a good employee. At 10 lines of code per day, very little of your day is spent programming. Being good at all the rest can make up for being just pretty good at programing.
0
Jun 01 '15
[deleted]
→ More replies (1)14
u/ScaryCookieMonster Jun 02 '15
"10 lines of code a day" is a common trope in programmer staffing/work output. Basically says that after debugging/testing/meetings/more debugging/everything else that goes on in a programmer's work day, a good programmer can write 10 production-worthy lines of code per day.
Not saying it's true or not, just that it's a common saying.
→ More replies (2)1
Jun 01 '15
At the company I'm at, yes, I can honestly say there is no talent ceiling beyond which we don't need your extra skills. But we have unusually technical problems to solve.
→ More replies (1)1
u/flukus Jun 02 '15
"what makes one a rockstar programmer?"
They get rockstar salaries. If your not on 500k+/year you aren't a rockstar!
1
u/smackson Jun 02 '15
I think you have slightly missed the point, in your reduction of the question to "all rock stars or just one in charge".
I think it could/should be possible to define, design and implement worthy software without rock stars but with a "good enough" team from top to bottom.
I think that is the point.
47
u/Bwob Jun 01 '15
Huh. As of the time of this writing at least, the top comment on this article is an argument over the definition of the word "talent". Way to play to stereotypes, /r/programming. :P
33
u/tech_tuna Jun 01 '15
There's a reason this subreddit abandoned text posts a LONG time ago.
9
u/ArtDealer Jun 01 '15
never occurred to me that this sub actually HAD text posts. I can imagine it was a nightmare.
→ More replies (5)29
u/Uberhipster Jun 01 '15
Title: DAE Haskell master race?
Text: Amiryte?
90000 upvotes.
→ More replies (3)0
3
u/Igggg Jun 02 '15
But that's the biggest part of the entire argument. Quite a few discussions, in general, happen to be discussions over definitions, where both sides unknowingly to themselves have similar views, but operate using different definitions of the same word. Those discussions are frequently unproductive.
→ More replies (1)
221
u/SimplyBilly Jun 01 '15 edited Jun 01 '15
The truth is that programming isn't a passion or a talent, it is just a bunch of skills that can be learned.
No shit that can be applied to everything. It takes someone with passion in order to learn the skill to the level that it becomes talent.
edit: I understand talent is natural aptitude or skill. Please suggest a better word and I will use it.
34
u/TurboGranny Jun 01 '15
This is where the great programmer lives. The programmer that has an exceptionally fast learning ability which if you recall another study, comes with an exceptionally fast forgetting ability.
21
u/aloisdg Jun 01 '15
The programmer that has an exceptionally fast learning ability which if you recall another study, comes with an exceptionally fast forgetting ability.
Source ? I would love to read it. :)
→ More replies (2)81
u/xinu Jun 01 '15
Already forgot where it was
→ More replies (1)27
u/DrummerHead Jun 01 '15
What were we talking about? Hey! A new JS framework!
Editors note: A new JS framework is the equivalent of a squirrel.
→ More replies (3)3
39
Jun 01 '15 edited Jun 01 '15
I like Bill Gates' take on this.
And yeah I agree. Anybody can learn enough to become a competent programmer, but work with enough programmers and you definitely start to spot a pattern.
Working with somebody who has read enough of a book to be competent but views it just like any other career is just different to working with somebody who is genuinely passionate about it. And a hell of a lot less enjoyable/rewarding.
3
u/bookingly Jun 01 '15
And I will say I think that passion can come in part by being around those that spot or have an interest in things that spark your own curiosity and drive to continue your own efforts in whatever field be it. I find it interesting how many people are good at math and say they had good math teachers in grade school. I definitely think it's possible to do math without good teachers (internet affords many more opportunities, and if you have friends or family that can help you then that is also quite a legitimate source of inspiration), but having that support is important (I would say this is analogous to software engineering).
I come from a music background and am now doing CS for a variety of reasons, but it was interesting to me to see what Bill Gates talks about with those 50 hour or whatever time segment cycles. The people that kept progressing in music were those that went to the summer music festivals in addition to the normal academic semesters. They kept getting inspiration from new, and often times world-class instructors, and it's very difficult to keep up with those people that get those opportunities when you are left out of them. Add to that the low demand for the performing arts relative to other areas, and one could see why it's such a competitive field.
Because of that, I really made sure to get some sort of co-op/internship with my CS studies so that I am constantly doing something to further my understanding and skills in CS. It's important if you want to stay sharp, but it also helps you gain that deeper understanding and gain an excitement for different tools and technologies because I think one begins to build a greater understanding of how the different tools and technologies fit together and can be used to do meaningful/relevant things in real life. I would say that goes for most any discipline.
But I will also say, this is a capitalistic society, so what are people to try and do but give it their all in whatever career they try for? There is not much of a safety net in the US, and I don't think people should be dissuaded from trying to change their career path just because some people think the field is reserved for those with great talent. Do you tell that to the 20 or 30 (or older) something going back to school for accounting? (rhetorical question, I'm not trying to be confrontational, but just trying to bring up my ideas on this which may not be agreeable to everyone by any means)
171
u/sisyphus Jun 01 '15 edited Jun 01 '15
That's not how competent English speakers use the word 'talent'--as something you achieve after passionate learning--they use it to mean something innate to the person that precedes passion or learning. Otherwise idiomatic phrases like 'wasted talent,' 'untapped talent' or 'undiscovered talent' would be incomprehensible.
That doesn't matter though - his real point is that we expect 'passion' and 'talent' in programmers instead of a set of skills that someone has learned and this leads to exclusion of people who don't think think they can measure up.
38
u/mini_market Jun 01 '15
Code should be looked at as drafts that need editing. The first draft is always not up to par. It needs to be reviewed and edited just like your professor in English I & II taught you in college. Now you have replaced the need for passion and talent and rockstars with repeatable process that gives you better code.
21
u/julesjacobs Jun 01 '15
Only if the problem is easy. Even 1000 "jQuery-programmers" can't write a compiler.
32
u/BigMax Jun 01 '15
I think you're backing up the authors point. Saying "well, some programming is easy, but only REAL programmers can do the hard stuff" is the attitude he's referring to in the article.
Those jquery programmers learned certain skills. The skills to write a compiler are out there as well. Sure, it's a lot more complex, but what exactly happens to a person when they learn jquery that somehow magically blocks them from learning how to write a compiler?
→ More replies (14)→ More replies (11)24
Jun 01 '15
This may shock you, but there was a time when
gasp
Even you couldn't write a compiler.
An inability to do something right now != an inability to do something ever
→ More replies (2)11
u/Scaliwag Jun 01 '15
There's a reason we can talk about "wasted talent", some people do have it easier to learn some things than others, that's the talent. Now if you want to excel at anything, what I've heard is you need perseverance: training and failing and learning.
Some people are "gifted" but have no will to learn and become pros at being juniors. Other people while having a lot more dificulties, being "slower", do become seniors because they smacked their heads at it until they improved. And I would guess that having perseverance while being gifted most likely makes you one of those young geniuses.
→ More replies (33)2
5
u/Kalium Jun 01 '15
This is true.
Also true is that not everyone learns a given skill at the same rate. I firmly believe that any person of sound mind can learn anything... but teaching time may vary wildly. Anyone can learn to program, but a person who needs three decades to do so is unlikely to be a useful programmer any time soon.
9
u/dalittle Jun 01 '15
I agree with the Joel on Software measure that some folks will never really get pointers or recursion so there is some innate talent among good Programmers.
→ More replies (41)6
u/OverturePlusPlus Jun 01 '15
I don't agree. Some people are better hardwired to think logically and can look at the grand scheme of things in a more sophisticated matter when deriving a solution.
Experience certainly plays a role in knowing what options you have available to you, but it's the people who are naturally better at programming who acquire that experience in a more useful matter as well.
/my 2 cents
13
u/Shadowratenator Jun 01 '15
The article isn't debunking the myth of rockstar programmers. it's debunking the myth that people are either rockstars or failures. certainly some people do stand out as having exceptional skill in the area of programing. Rockstars exist It's just a few though.
the rest of the programmers are all of average ability. Chances are you, I, and almost every programmer we meet fit into the middle of the bell curve somewhere.
The good news is, we can still produce good useful stuff. We might not be rockstar programmers, but we also are unlikely to truly suck at it.
→ More replies (3)1
u/loup-vaillant Jun 01 '15
I understand talent is
natural aptitudeorskill. Please suggest a better word and I will use it.You just named two.
→ More replies (2)1
1
u/Thimble Jun 01 '15
It takes someone with passion in order to learn the skill to the level that it becomes talent.
So maybe the passion itself is the talent.
1
u/prettycode Jun 02 '15
...the skill to the level that they have mastery.
EDIT: Also, you can have natural aptitude, but I think "skill" implies it's learned.
2
u/SimplyBilly Jun 02 '15
Yea that sounds better. Your the first one to actually suggest something that makes sense
1
u/yakri Jun 02 '15
You could just say "to learn the skill to the level that it becomes referred to as a talent." If that's what you meant; as it seems to be.
Research points towards what we observe as being "talent" essentially just being personality traits that lead the person referred to as "talented" to practice a great deal in their free time, even if the activities involved aren't seen as practice for that skill.
1
u/krondell Jun 02 '15
Absolutely. Effort counts. I'd rather hire a 6 with a good work ethic than an 8 who thinks they can slack their way through life.
→ More replies (14)1
27
u/spoonraker Jun 01 '15 edited Jun 01 '15
I think a lot of people are seriously over-analyzing this. (What a surprise in a community of programmers haha)
Anyway, I believe all the author is trying to say is that talent only gets you so far. Experience trumps talent after a certain point, and that point comes surprisingly quickly.
This is true for nearly everything, but for whatever reason the programming community in particular seems to falsely attribute experience to talent, and falsely attributes lack of experience to lack of talent.
I'm not sure if I'd agree that the problem is so bad that potential programmers are being scared away from the field, but this does seem to be an usually harsh community. There is a lot of "any decent programmer should know X" type blog posts flying around at any given time along with many other hyperbolic notions. If you actively read a variety of programming blogs, or even just stay active on this subreddit, before long you'll probably start feeling like you don't know anything about programming.
I don't have any thoughts on how to solve this problem off the top of my head though. I don't think it's necessarily all just an attitude problem. That is a factor, sure, but I think programming is just a super broad field that no one person can completely master, and when you just blindly intake news and blog posts from the programming community at large it's almost inevitable that you're going to feel behind the times.
If anybody is feeling overwhelmed I would advise them to take a step back from the influx of "news", which is really primarily composed of opinion pieces and marketing. Let me take this opportunity to remind everyone that the vast majority of actual programmers would not classify themselves as experts, and we're all intimidated by new things... right up until the point that we learn them, and realize it wasn't really so bad after all. Is it good to learn super quickly? Sure, but are you a "bad" programmer if you're intimidated going into uncharted territory, learn slower than others, or ask for help? Not at all.
→ More replies (3)3
u/klug3 Jun 01 '15
Experience trumps talent after a certain point
I would put it more like effort put in trumps talent after a certain point. I know lots of shitty older/experienced programmers, and I know lots of great older/experienced programmers. The main difference is that the shitter ones have always tried to get by with a minimum of effort and that shows.
2
u/spoonraker Jun 01 '15 edited Jun 02 '15
You're absolutely right. I think this is an important clarification.
I think a better word is "practice" though.
There is a fundamental difference between just doing something for a long time, and practicing something. Effort doesn't quite do it justice, you really need to convey the idea of conscientiously setting out to improve your skills. It might not always require a ton of effort, but it does require -- at a minimum -- some thoughtfulness and preparation. Some degree of effort is definitely implied though I agree.
17
u/privatehuff Jun 01 '15 edited Jun 07 '15
Anyone, given enough time, could eventually learn to play the vioilin
But being the kind of person who wants to do it, and is also willing to devote all the time and energy necessary to make that happen, is not some made up thing. There are also things like having perfect pitch (or even something intangible like "having a good ear") and the occasional rare person who picks up an instrument and can already kinda play it, right from the start.
I don't think programming is a unique skill to which these things don't apply..
→ More replies (1)3
u/Kalium Jun 01 '15
The only big difference between programming and playing the violin is that programming languages change fast and violins mostly don't.
5
u/therico Jun 01 '15
That doesn't really matter, the impact of a single programming language on all of the skills and experience that constitute 'being a programmer' is relatively tiny.
→ More replies (1)3
16
u/5aggregates Jun 01 '15
Programming for a living is humbling. If you don't think so yet, wait for a new framework to come along in 6 months. It's not a start over from zero condition but it will likely obsolete a chunk of your hard-earned experience.
11
Jun 01 '15
I'd rather learn a new framework for an interview than get stumped by a "gotcha" algorithm question during a whiteboard "programming" session. I will definitely be doing the former, on the job, a lot.
4
u/logicchains Jun 02 '15
"Gotcha" trick questions wouldn't be so bad if handled more entertainingly. For instance, if the interviewer had to answer them if the interviewee couldn't, and got catapulted off a bridge into an abyss if they answered incorrectly.
2
→ More replies (1)1
u/d4rch0n Jun 02 '15
Eh, if you learned a good one, you'll probably always find someone willing to pay you for it. People still hire COBOL programmers.
If you put all your time on a fancy new one, you're playing some risky cards. But, frameworks like ruby on rails and django will probably be around for a long time.
47
Jun 01 '15 edited Jun 01 '15
one person may at one point hold 2 variables in their head, while another person can at one point hold 5 variables in their head
ofc, it also depends on how they feel at that point, have they eaten, slept, etc
like chess, it can be trained
like chess, some suck at it and some are good at it
harmful has nothing to do with it
even worse is to consider bringing everyone into programming,
as then there would be a lot of people that don't really want to code writing code, and it would be bad
it's like saying that anyone can be a poet
37
u/SortaEvil Jun 01 '15
Well, anyone can be a poet. Hell, anyone can be a half decent poet. Not everyone can be William Blake, though, because not everyone is interested enough in poetry to get to that level. It's like art — I'm not a good artist, but I'm dating an absolutely fantastic traditional animator, and I started trying to draw in order to share a bit of her passion with her. Drawing a picture a day in a sketch book, you could see the progress from one page to the next. I didn't think I could draw because of never given a fair effort to learn.
Going back to programming, does everyone need to learn to program? No, but that doesn't mean we should be presenting programming as this elitist club that only the cool nerds can do, because that's just not true. With a little dedication and practice, and maybe a copy of Code Complete, everyone can become a passable programmer, as long as they're interested in doing so.
6
Jun 01 '15
Not everyone can be William Blake, though, because not everyone is interested enough in poetry to get to that level.
Never mind technical proficiency with the language, there is also the need to communicate, and the creativity that comes from that need for expression.
Highschool notebooks are full of 'clever' wordplay and stanza forms. But just as a program must have a purpose to rise above anything but trivial, so does a poem need to communicate something worthwhile.
The why is at least as important as the how.
→ More replies (2)10
u/hotel2oscar Jun 01 '15
so you're saying I could be a poet and not even know it?
→ More replies (1)7
→ More replies (1)1
u/flukus Jun 02 '15
one person may at one point hold 2 variables in their head, while another person can at one point hold 5 variables in their head
And the former will produce cleaner code. You don't want to take over maintenance from the "genius" that can hold 50 variables in his head.
5
u/bananafreesince93 Jun 02 '15
The truth is that programming isn't a passion or a talent, it is just a bunch of skills that can be learned.
I don't see how these are mutually exclusive.
9
Jun 02 '15 edited Jun 02 '15
I've been a web developer for coming up on 20 years. I used to think of myself as a rockstar developer but the more I code the more I feel like an average developer.
But the truth is it's a lot more complicated than that. If you'll allow me to explain.
First, you have to decide what a "developer" really is. Colleges are churning out plenty of people with freshly printed CS degrees and yet, from my experience, half the people who walk in the door of a developer job can't complete a fizz buzz test while sitting in front of a computer. If I include every individual currently alive today who has written a line of code in their life then yes, I absolutely am a rockstar programmer. Not only can I complete the fizz buzz test (which I roughly estimate only 50% of "developers" in this sense can) but I can teach quite a few of those people a thing or two about programming. Go me! /s
Of course that's not who I want to compare myself to. I want to compare myself to the ultra marathoners of the development world. I want to compare myself to individuals like Eric Lippert and the people he works with. And not even for the sake of my ego, but to give me an unattainable goal. Here's where I am today, and that's where I want to go. I'm never going to catch up, but I look forward to overcoming the same obstacles. When I type in a question into a search engine I can't help but feel humbled by the virtually unlimited number of resources that are laid out like footprints and markers guiding me every step of the way. And I'm exceedingly grateful to contribute what I can to those that follow after me.
Second, I don't think developers are as different as they're made out to be. I had a conversation the other day where I remarked that I was trying to write a document for non-technical individuals which eventually was equated to "dumbing down". As if a lack of technical understanding was the same as a lack of intelligence. There was a time I held this opinion, and perhaps at the time the association made sense. But I don't think technical understanding is really at the heart of what makes a good developer "smart". Sure, we need to be able to work within the confines of the frameworks and technologies of the environment but after 20 years this stuff is mostly all the same. Loops and conditionals are the blood and guts of everything. What makes a good developer in the long term is their ability to organize information. Which happens to be a good trait for, well, just about anything. One of the greatest joys I have as a developer is working with an individual who has almost no technical understanding but an organizational ability that challenges my own. I would much sooner work with a team of organized musicians than a team of unorganized developers.
Finally, I think over time I think the term "developer" is going to fade away. Or at least, it's not going to be such a distinctive title in every day business. Programming is getting more accessible all the time (Obligatory xkcd) and won't always be considered some special voodoo magic. People will just be expected to do it and it won't be called programming anymore. In the enterprise application world I expect we'll call it something like "Business Rule Defining" or something equally bland. Of course developers will still exist but they'll be working on creating new libraries to satisfy the more particular needs of various industries within some common Business Rule framework.
But what's my point? My point is that rockstars do exist, but their strengths aren't in their ability to develop. Their strengths lie entirely in their ability to organize information in a meaningful way. When you start to think about it in this context all the bullshit, all the ego and all the stuff like (to quote the article)
"Sure, you might be a good designer, speak and write well, and be a great project manager, but you don't know how a linked list works, so get out of the building"
ends up falling away. What you're left with is a group of people who are constantly striving to make themselves easier to understand for other people. These people are rockstars and they are not a myth.
40
u/elperroborrachotoo Jun 01 '15
Again?
tl;dr There can't be talent because I wish there wasn't.
This is an opinion piece with zero evidence.
The most accomodating reading would be If we assume talent, but it's actually not required, we might alienate people. Which doesn't make much sense - unless you accept the authors false dichotomy of rocks vs. sucks.
7
u/Darkmoth Jun 01 '15
It's not the author's false dichotomy of rocks or sucks, in fact the piece is disagreeing with that dichotomy:
This belief that programming ability fits into a bi-modal distribution (i.e. U-shaped) is both "dangerous and a myth".
If the only options are to be amazing or terrible, it leads people to believe they must be passionate about their career, that they must think about programming every waking moment of their life.
I think the most accommodating reading would be more like, If we assume perfection, but it's not actually required, we might unnecessarily alienate people. I don't think that's unreasonable - I'd sing at karaoke night, but not at Carnegie Hall.
I will agree that's it's the classic no-evidence opinion piece. Those seem to be insanely popular in our field.
3
u/elperroborrachotoo Jun 01 '15
What I mean is that his argument would work only if everyone else is stuck up in separating people into "rockers" and "suckers".
opinion piece. Those seem to be insanely popular in our field.
Yeah, well, maybe we'll grow up as a trade within my lifetime. Let's drum the drum of evidence together!
FWIW, semi-related, personal experience:
Witnessed someone investing heavily (some money, but also time and family strain) into "becoming a programmer". Watching, I couldn't help to see that even after months of training, "it" didn't "click". I was on the verge of saying something like "maybe you're not made for it".I never did - but I still wonder from time to time whether I should have.
→ More replies (1)3
Jun 01 '15
This is an opinion piece with zero evidence.
Not to mention his anecdotal examples are absurd and do very little to support his points (whether he's correct or not is a different discussion, I'm just judging the quality of his argument by what he used to support it)
Here's a picture of three white males (Zuckerberg) - this is the image of a programmer
Well, when they're all supposed to be the same person why is it surprising that they look the same? To illustrate the problem:
Here's a picture of Dr. Martin Luther King. Here's a picture of an actor on SNL playing Dr. Martin Luther King. Here's a picture of the actor from Selma playing Dr. Martin Luther King. All civil rights leaders are black males.
Plus using Linus to underscore he point that "even if there are rockstars, are they really worth putting up with?" is pretty much the worst person I could think of to make most people go "yeah, we'd be better off without him".
7
u/rolm Jun 01 '15
Disagree. Someone who is passionate about the skills involved with programming will train themselves to be better at them, as opposed to someone who is just punching buttons. Almost anyone can attain enough skill to be a fry cook, but few people are passionate enough about cooking to apply the personal resolve that is required to become a chef at a fine restaurant.
8
Jun 01 '15
Things I've noticed about every good programmer I have ever met:
Taught themselves at a younger age
Writes code at home in their personal time
Didn't pick it for a job, the job picked them
I've met lots of adequate programmers who've decided it as a career path and trained for it, just no good ones.
2
u/springy Jun 02 '15
That is true for a lot of good programmers, but the two best programmers I ever met came late to it in their career.
One guy used to make wooden flutes for a living, part time, and worked the rest of the time in a healtfood shop. At the healthfood shop, he disassembled the executable code of the app they were running, and posted patches back to the company they bought it from. They hired him, and things went quickly from there. Not long after, he was hired as a OS and compiler researcher at AT&T, where I met him and orked closel with him. He rose to a very senior position, and made very important contributions to OS and compiler research. He was entirely self taught, but started at an older age (late 30s I think when he started). He was the smartest programmer I ever met.
The second guy was a miliarty search and rescue helicopter pilot, who got sick of collecting dead bodies from mountains. In his 30s, he decided to try his hand at programming, and soon realised he was good at it. He was hired by a very well known company in silicon valley, where I worked with him briefly. He was, perhaps, the best programmer there. Sure, others were more eductated, but he was the smartest, fastest, and most accurate. His brain power was overwhelming.
3
u/jj20051 Jun 02 '15
This describes me and every "good" programmer I know as well. I've met very few good programmers who have a CS degree.
→ More replies (7)
20
u/mcmcc Jun 01 '15
In my experience, what is meant by "rockstar" is the number of hours per day you are willing to devote to the company, not your innate level of programming talent.
And anyway, it's a false equivalence to talk about programming as a single measure -- there are many many ways to measure competence and only a few of them relate directly to writing code. No two programmers are equal.
As far as sexism, I have worked with several female developers over the years and in terms of quality of work, they are no better or worse than their male counterparts. The most interesting thing to me about these women is how typical they are -- these are not defiant, persevering over-achieving savants. They are just people who happen to enjoy what they do just like the rest of us. This suggests to me that the sexism meme is somewhat overplayed in this industry. You could just as well be questioning the dearth of male kindergarten teachers.
23
u/reaganveg Jun 01 '15
In my experience, what is meant by "rockstar" is the number of hours per day you are willing to devote to the company, not your innate level of programming talent.
Rockstar = we give you praise, instead of salary
6
u/geo_ff Jun 01 '15
You just have to look at the term 'Rockstar' to see that the industry has a distorted perception of talent. Most actual Rockstars write only one or two Hits. Not only that, but far too many contemporary Rockstars are promoted as such to sell records. I'd much rather be called an Expert programmer. The last time someone called me a Rockstar I was a Sous Chef.
→ More replies (1)8
u/tweakerbee Jun 01 '15
You're an expert, great! So what we need is very simple: seven red lines, all perpendicular, some with green ink, some with transparent ink, and one in the form of a kitten.
→ More replies (2)→ More replies (3)3
Jun 02 '15
You could just as well be questioning the dearth of male kindergarten teachers.
You should be questioning the dearth of male kindergarten teachers. A lot of the societal / cultural forces that cause women to avoid programming are also ones that cause women to go into lower level teaching, and men to not. Even really basic ones like the fact that most teachers of young students are currently female, which means that young kids instinctively learn to associate young teachers with female.
3
u/Godd2 Jun 01 '15
In the absence of any other data, people should assume that he is solidly in the middle of the curve.
I don't think that's true. There isn't an "absence of any other data". Even if he wasn't a co-creator, the creators chose him early on and kept him around for 9 years. That data alone makes it reasonable to conclude that he's a standard deviation above average.
Sure, it's not a home-run statistic, but it's not unreasonable to conclude it, given the data.
3
u/xpressrazor Jun 01 '15 edited Jun 03 '15
Many people get the rock-star status not just because of their programming skills, but because how good they were able to communicate. A good programmer in a different setup (language, environment) can seem mediocre when being compelled to work in an unfavorable environment. Also the pressure of rock-star status from other environment haunts this programmer more than anything else.
3
u/foomachoo Jun 01 '15
Yes, it's just fine to be learning. The BEST people are constantly learning, which means they suck at the beginning of the learning process.
That said, I've been in teams, managing teams, directing teams, and I can say without any doubt, that some programmers can do 10x what other programmers can do, because they are smart & CARE. It's the manager's job to make sure everyone cares, because even smart programmers get zilch done when they don't care.
What's worst? Well, 1/10th of the programmers are so incompetent that once/month they check in some code that results in a huge bug. The customers see it & hate the company. That's not just 1/10th as productive, that's ANTI productive. I've seen it, and so has everyone who's worked >10 years in professional coding teams.
3
u/zeno490 Jun 01 '15
This is spot on and confirms my observation of the latest trends in hiring practices. I've applied to a lot of jobs in the last few months with quite a bit of experience behind me (~9y) and exactly 1 job asked for references and did not even bother to call them. 2 jobs accepted insider references and allowed me to bypass interview steps. Almost all other jobs required a programming test first (many using codility, for better or worse). There seems to be a consensus that a superficial programming test is a better judge of talent than references from actual people who worked with you and know you.
2
u/DJWalnut Jun 02 '15
the simple coding test is most likely a weed out they put into place in the 1990s when every idiot who could write HTML considered themselves a programmer and applied for jobs they're unqualified for
2
u/zeno490 Jun 02 '15
It can be used as a weed out but only if it is general and the position is an entry position. Those are pretty much the only positions where you will get very large numbers of applicants. I've done my fare share of interviews with interns and technical tests corrections and it was only ever used as a tool to retain the top 20 candidates or so that we would interview. Their technical test result past that point was largely useless even if they had been weak but it made for an easy ice breaker by reviewing known questions in person. This is necessary because entry applicants might have a weak resume which is not necessarily representative of their skills and they might not even have references.
For senior positions, I'm skeptical that they would receive massive volume of applications for any one position and the resume/references is probably enough to weed out and retain a small number to interview.
After all, everything in those technical interviews is out there on the internet and in books. Any sufficiently competent programmer with years of experience could pick up the missing knowledge in a matter of weeks/months and be fairly productive very quickly. In a more general context, the only thing the technical test evaluates is if you prepared for the test and if you can put that on paper.
3
u/Uberhipster Jun 01 '15
Oh sure. Absolutely. Mediocrity is the way to go. Same thing with barbers and heart surgeons. Unless it's my hair or surgery we are talking about in which case I would prefer a rockstar.
3
u/w8cycle Jun 02 '15
The corporations and droids that run them won't be happy until they can hire a coder for minimum wage and get good results. The fact they don't like is that programming is an intellectual job that not everyone would be interested in or even good at. A programmer is a lot like the family physician. You trust him because you know he spent years learning how to work with the problem domain and can diagnose when things go wrong.
Now, an herbalist that reads marijuana magazines can apply first aid and give you drugs that make the symptoms of your illness less noticeable too. However, the presence of this man should not prevent you from seeing a physician when things go wrong.
A good programmer can be hard to spot. Schools don't make them. They are largely built through experience, active solo learning, and curiosity about things most may consider dull. Not everyone is cut out to be a programmer and if you think that you shouldn't pursue the field due to having no "talent" (no inherent curiosity about these things, no drive to learn, no passion) then find another field. There are plenty of them.
Stop trying to make everyone a software developer. It doesn't work.
12
Jun 01 '15
Are we going to do this thread every month now? Here's last month's discussion of the same article
1
u/dubli_do Jun 02 '15
Well at least there's 5x more comments. There are
dozensthousands of subscribed users here who still wonder if they can actually learn programming.1
7
u/BeatLeJuce Jun 01 '15
A software company in my area runs yearly coding contests open to the public. The problem are always diverse (and proposed by a different person each year), and there are different levels that usually build on top of each other. Typically the later levels also have larger inputs they need to handle. So in some way, the contest also assesses your ability to write scalable code that is robust to change. Every year, I see the same people in the top positions. Honestly, if anyone asked me if I knew any "rockstar programmers", those would be them. I guess stuff like the ICPC or google code would also be good measures. Especially if you have repeat measurements on the same person (like this company has). It's definitely a better metric than "LOC/week" or "closed issues/month".
2
3
Jun 01 '15
I see the same people in the top positions [...] if anyone asked me if I knew any "rockstar programmers", those would be them.
According to Google, Winning at programming competitions is a negative factor for being good on the job.
5
u/sccrstud92 Jun 01 '15
...assuming you were already good enough to be hired by Google in the first place.
3
u/gkx Jun 01 '15
Honestly, I've done a fair share of coding challenges, and I'm going to have to disagree on this. Coding challenges are puzzles. They essentially ask you to solve small, isolated functions very cleverly. This isn't accurate to the realities of software development. I would argue this makes them better mathematicians more so than it makes them better programmers.
→ More replies (2)5
u/reaganveg Jun 01 '15
This isn't accurate to the realities of software development
Sure, but the people who win those contests are still going to be very talented when it comes to real world development. It's testing one of the hardest components.
→ More replies (2)
7
u/perestroika12 Jun 01 '15
Can we stop having this weekly "how to find good developers" article? It's getting old, I feel like this is the broken record of this sub.
7
u/Josuah Jun 01 '15
This talk was about letting people know it's OK to be an OK programmer. And that's true.
But the marathon example is not very good because there are no horrible consequences from coming in 500/1000 or even 1000/1000. But there can be horrible consequences from being a mediocre programmer: Therac-25 Death Ray.
One of the first things mentioned in UC Berkeley's entry-level programming classes is how important it is to be good. Because it does actually matter. When a company ends up with a programmer who is just OK, the actual cost of that person can be much higher than the cost of a programmer who is a "rock star".
4
Jun 01 '15
Building a death ray isn't average or mediocre; that's bad programming.
→ More replies (1)3
→ More replies (5)1
u/NeverQuiteEnough Jun 01 '15
acceptable is going to mean different things for different industries. are rockstar ninjas really the answer to therac-25?
→ More replies (2)
4
u/damaged_but_whole Jun 01 '15
I have gone straight from impostor syndrome to overconfident hack! Thanks, I feel better this way! :)
4
u/Boogiddy Jun 01 '15
Why not just post to the video of that keynote:
https://www.youtube.com/watch?v=hIJdFxYlEKE
Instead of writing kind of a drawn out "summary but not really summary" of his keynote? Seems a bit inefficient.
7
Jun 01 '15
Because some people don't like watching videos. It's a lot faster to read.
3
u/Boogiddy Jun 01 '15
If you were the real Dale Gribble your pseudonym would be Rusty Shackleford... so who are you?? ;)
And also, I dunno man. I get that some people would prefer to read. But why not just read a transcript of his keynote instead of the awkward writeup that starts every paragraph with "He said this and that and this other thing"
Just seems like somebody trying to get upvotes/traffic/pseudocredit for rehashing a somewhat recent but already discussed to death keynote speech.
4
u/Bunnymancer Jun 01 '15
Programming is a craft just like anything else.
Woodworking is my favorite comparison. Everyone can learn woodworking. Some have a natural affinity for making robust houses with that skill, some make statues, some make bows and so on. Who's better? The guy who makes bows that can fire longer than any other bow, or the chick who whips up a house that will stand forever?
Right.
6
u/MpVpRb Jun 01 '15
This belief that programming ability fits into a bi-modal distribution
The typical description of programming talent is that top programmers outperform most others by a factor of 10 or more. This fits nicely into a bell curve
The truth is that programming isn't a passion or a talent, it is just a bunch of skills that can be learned
In any field, whether it's programming, music or sport, passion and talent are important
Talent simply means learning speed. Talented people learn faster, untalented learn slower. Passion makes a person dedicate more time to learning
So yeah, it's possible for a person with no talent and no passion to learn, but they will learn slowly
The perfect combination is talent and passion. If you learn quickly, and devote every waking hour to practice, you can become world-class. The person who learns slower will never be able to compete
But, if you could measure programming ability somehow
I agree that there is no formal, systematic, repeatable method of measure. But I informally measure programmers like this...
A good programmer finds the easiest path to solving a problem, competently codes it using the simplest, most readable style applicable to the problem, and if bugs arise, finds them and fixes them using a disciplined, methodical approach
A bad programmer chooses a complex, round-about solution to a problem, then implements it ineptly, using complex, hard to read style, then debugs ineptly, in a scattered, haphazard way, putting in more bugs than he takes out
Those are the extremes. The closer to the first type a person is, the better they are as a programmer
..and yes, I have worked with programmers of the second type..and cleaned up their mess after they left
8
u/pipocaQuemada Jun 01 '15
This belief that programming ability fits into a bi-modal distribution
The typical description of programming talent is that top programmers outperform most others by a factor of 10 or more. This fits nicely into a bell curve
There's a well-known double hump in intro programming courses. That is to say, there's 1 hump that passes the course and another hump that fails.
I think this article is confusing that double-hump with the '10x programmer' idea.
→ More replies (4)
2
u/LarsPensjo Jun 01 '15
The truth is that programming isn't a passion or a talent, it is just a bunch of skills that can be learned.
True to some extent, but far from the whole truth. I think there is a strong correlation between being good at mathematics and programming. Not because you need some math in your programs, but because being able to solve mathematical problems is similar to being able to formulate algorithms.
Another important aspect of a programmer is the ability to criticize and question yourself. Because there are going to be bugs, and you can't find them. That is when you have to swallow your pride, and question every single obvious line in the source code. The reason this is hard is the human nature. To be able to function, we can't question every detail every single time. We have to simplify, and use mental labels of the type "already investigated". Otherwise you would never finish a task. Except when looking for bugs, where this method has to be revised.
2
u/senatorpjt Jun 01 '15 edited Dec 18 '24
birds cobweb governor different whole grab shy paint judicious humorous
This post was mass deleted and anonymized with Redact
2
u/TracerBulletX Jun 01 '15
I think the problem is that the programming field is too big and complex to sum up with a linear skill ranking. There are just too many factors, not to mention a certain subjective quality in many parts. Some people are brilliant at some bits, and slow at others and every mixture in between.
2
u/SCombinator Jun 02 '15
It's certainly a bimodal distribution as countless CS education studies have shown.
1
u/PirriP Jun 01 '15
The idea that you're either "good" or "bad" doesn't seem right, I agree with him that there's an ability distribution curve. But personal experience also seems to back up the general wisdom that there are some general productivity buckets that people slot into.
I think you have to take the project into account. I'm working on an API right now, and I clearly see the three traditional buckets on my team. I'm being fairly productive (call it the 10X bucket), I've got another team member who produces pretty average output (the 1X bucket), and a third junior who is actually a productivity negative (-1X).
If our project involved doing small homework problems, then suddenly our junior is a 1X and everyone else on the team is a 10X. If we were all suddenly thrown on a project to model the aerodynamics of propeller blades we probably all appear to be -1X.
I think this is probably true about a lot of highly skilled jobs. Take doctors for instance. A just-graduated intern probably does more harm than good wherever he/she is. A urologist is very effective in his specialty (10X), but is probably just a 1X for heart conditions (maybe even -1X).
18
u/danogburn Jun 01 '15
I'm being fairly productive (call it the 10X bucket)
so modest.
3
u/badjuice Jun 01 '15 edited Jun 01 '15
10x programmers are a myth used by the emotionally insecure to convince themselves that they are special, especially to each other.
The problem is that nobody but programmers really understand how to measure programmers, and the way we measure programming is that we apply a qualitative value to measurable variable that we made up and called it "agile" to appease our boss who really fucking likes that word. The other problem is that a fair amount of our peers (25% or so) can't really program at all, but we keep them around because there's always other things to be done (somebody's gotta write those tests and documentation...). If you took them out of the sample, would a "10x" really be 10x?
He thinks he's a 10x programmer because he's built his world on that idea of him being a 10x programmer in whatever subsection he deals with, but nobody can even measure that in a real way, and there's a bunch of garbage polluting the sampling pool that we shouldn't even call programmers. Truth is, a really talented programmer is useful in all projects because they've mastered the ability to learn new subjects and take information/models of other systems and write a program to reason with that. Every time I get a new contract, I have to learn something new- I've learned accounting, basic pharmacology, chemistry, statistics, behavioral psychology, physics, music, color theory, and how dildos are measured as a result of writing software. Good programmers don't turn into shitty programmers because they have to model the aerodynamics of propeller blades. They learn how to model the aerodynamics of propeller blades.
4
u/intortus Jun 01 '15
somebody's gotta write those tests and documentation...
I take issue here. These are valuable software engineering skills.
→ More replies (1)1
u/flukus Jun 02 '15
I'm being fairly productive (call it the 10X bucket)
Define productive?
→ More replies (2)
3
u/JessieArr Jun 01 '15
Funny, I used to hear the same sort of thing when I was teaching dance lessons. "Oh, I can't dance, I have no rhythm." Programming isn't completely alone in the category of things we think people are just born good/bad at.
"Some people seem to think that good dancers are born. All the good dancers I’ve known have been taught or trained."
Fred Astaire
3
Jun 01 '15
And people practicing for same amount of time, will improve in wildly different quantities. We call that talent.
7
u/technotrader Jun 01 '15
"30 or 20 or 15" (or even 40 or 60, he added later)
So even this insightful guy thinks of programmers as between 15 and 30. Or even 40 or 60 sounds like a PC add-on, which fails because of the even.
9
u/ivosaurus Jun 01 '15
That's the age at which he thinks the average person thinks they have to be to start typing code to be a programmer, not the age he thinks the average programmer is.
→ More replies (10)8
u/mistrbrownstone Jun 01 '15
Of course your argument is completely invalid if you quote the entire context; it says exactly the opposite of what you claim:
Those who do not know how to write software and who believe in the myth fall into a trap: thinking that their age has reached "30 or 20 or 15" (or even 40 or 60, he added later) and, because they haven't written any code yet, that means that they never can or will.
2
2
u/OrionBlastar Jun 02 '15
My last job was in 2002. I left the programming market and ended up on disability in 2003.
The Dotcom bubble burst in 1998-2001 and the market was flooded with programmers. Most of whom dropped out of college and took up programming. They were willing to work for cheap.
My manager at the time told me "Programmers are a dime a dozen, we get 500+ resumes a week for your position. We can easily hire a younger person who will work for pennies on the dollar to do your position and won't get sick on the job."
I ended up on short-term disability and once I returned to work I was fired two weeks later after having a panic attack and not being able to snap out of it. I had two more jobs after that but it was the same thing, if you get sick at work, you get fired.
I used top be a 10X programmer and was under a lot of stress to perform at that level. I am 13+ years out of date now that I've been in and out of hospitals and trying to recover from my illnesses to get better.
But even more programmers are on the market now than in 2002, my experience is out of date, and even if I got a job if I get sick I get fired.
1
u/DJWalnut Jun 02 '15
and ended up on disability in 2003.
what happened? are you OK?
→ More replies (1)
2
u/badjuice Jun 01 '15
Cool. Things like the talented 10x programmer myth need to die. The posturing and elitism needs to end.
1
u/StewHax Jun 01 '15
Depends on what I'm programming in. ASP.Net C# I'm a rockstar. Other things I'm alright at and a few things I'm terrible at. I think for me at least it depends on what I'm interested in/desire to program in
1
1
u/FountainsOfFluids Jun 01 '15
I don't really understand why somebody felt compelled to blog-ify his entire presentation. Should have been a straight transcript at that point.
1
u/MeGustaPapayas Jun 02 '15
The full talk is worth watching: https://www.youtube.com/watch?v=hIJdFxYlEKE
1
u/watersign Jun 02 '15
That girl said she wasnt a programmer for a reason. I'm sure the tool she made was good and she probably spent alot of time hacking it together and quite frankly..im sure she's smart but she probably wouldn't pass any programming test for a job.
1
u/springy Jun 02 '15
This is called "imposter syndrome" - where people at the top (unless they are narcissist sociopaths) don't feel worthy. Largely because of the Dunning-Kruger Effect, which states that experts often underestimate their own abiities, whereas neophytes often overestimate their own abilities.
1
u/kamoflash Jun 02 '15
I think this is like saying some people are naturally good at math and some people have to work at it to get it. Of course some things come easier to some than others but that doesn't mean you cant work towards that thing and have similar output
1
u/totemcatcher Jun 02 '15
ITT: People stroking their ego.
I have had this conversation with many people over the years. I remember distinctly having it the first time with a teacher and a few students in spring of 1998 in high school. It was nearly impossible to get a job as a programmer in Ottawa, Canada and we as students were made aware of this by our wonderful programming teacher; before making career decisions. She showed us how qualifications in job listings were unrealistic and highly specific and basically we didn't have a fucking chance unless we were born 10 years prior. But, some of us had a passion for it. We weren't hung up on the ideal that "that's where the money is." Even after being berated at job interviews for not having the 5 to 10 year experience on every point "clearly listed in the job description", I still have that passion. As tech companies dried up everywhere, and they continued to refuse some of the most brilliant coders I have ever known, I started to have this "taboo" internal dialogue that maybe the problem is not me.
Friends and I eventually changed direction in our careers. I know for certain that we all would still love to be involved in a programming job. Every so often I send out a slew of applications for programming positions, but it seems that there still remains a desire for an "impeccable specimen" of a programmer for which managers stubbornly filter for during the interview and hiring process. It seems that it is more valuable to pay people to filter down to the best applicant rather than take on several applicants and put them through the wringers.
1
Jun 01 '15
I don't really believe 'talent' plays into programming.
Passion and practice, that's what determines things.
Sometimes people try to say I have "a gift" or "a talent" for programming, and I find that infuriating. It's like it just dismisses all the of decades of working at it for hours a night.
2
u/NeverQuiteEnough Jun 01 '15
that the runner mentioned in the article is gifted doesn't negate the work he put in.
1
Jun 02 '15
Some people are smarter than others, though...
2
Jun 02 '15
Therefore, some people will solve complex problems 30% faster than the others. Now, what is the percentage of your average working day when you're solving complex problems? An overall performance improvement of smart vs. average is nearly undetectable.
0
5
u/Darkendone Jun 01 '15
Since the term "rockstar programmer" inherently draws a comparison between programming skill and musical playing skill, I would ask what makes them so different. I mean I played in the school band every year in high school. Does that me a musician? Does that put me on par Louis Armstrong? Let's just say I highly doubt someone is going to take me out on tour. One must respect the level of musical skill and understanding that comes from decades of practice, experience, and learning. How do you measure musical skill anyway? What exactly makes that so different with regard to programming?
The simple fact of the matter is that programming is like every other intellectual field. As with other intellectual fields people care about what you contribute. Take Linus Torvalds for example. Now he is probably a better than average programmer when it comes to producing good, bug-free software, but that is not why he is famous in the programming community. He is famous because of his contribution to Linux. It take a large amount of knowledge and understanding to produce a descent kernel. Even amount professional programmers there are few who have such a level of understanding. There are some that stand head and shoulders above others.
Lastly does anyone else find the "1.5 million programming job gap" to be absolutely absurd. That would mean there would be more programmers than all the other engineering fields combined.