3 ms·
Programming requires skill and diligence. Talent is nice to have but in no way necessary, and passion is totally orthogonal - I can only assume the word in this
by throwanem 10y ago
Programming requires skill and diligence. Talent is nice to have but in no way necessary, and passion is totally orthogonal - I can only assume the word in this context is a misnomer for enjoyment, but enjoyment is no substitute for discipline, because if you stop doing it when it's no longer fun, you probably won't ever build anything that's both useful and reliable. (jwz calls this the CADT model, and I've yet to see a better formulation of the concept.)
I do not like the "talented and passionate" rhetoric for two reasons more than its basic inaccuracy.
One is that it can be unnecessarily discouraging to people who are "merely" smart and good at what they do, but not yet experienced enough to question popular mythoi in the field - something I've seen in practice, and had to help people overcome.
The other reason arises from my own experience as a programmer who is talented, enthusiastic - I won't say "passionate" - and also entirely self-taught in the field since the age of six years. When I was in my late teens, the web became a thing, and I used it to further satisfy my eager interest in what other programmers had to say about the profession which I'd long since decided to make my own. Much of that was very similar to what you hear today - that you need talent and passion, and the rest is more or less negligible. Imagine my surprise when I discovered this was not the case! Imagine the crisis of confidence resulting from the discovery that the majority of being a professional programmer has nothing at all to do with your native inclination toward the field or the degree to which you can find enjoyment in writing code, but instead resolves around clearly understanding the problem that needs to be solved, and doing the hard, often dull work of solving it - not just the fun parts, but all of it - which oftentimes doesn't involve writing code at all.
In the end I got through it, and came out with the foundations of a solid professionalism which has served me extremely well since. But I could as easily have come to believe that I didn't have what it takes after all, and in any case that was a bad couple of years that really didn't need to have happened, and wouldn't have happened were the prevailing programmer culture, then and now, not so up itself that it casually throws around advice that's wrong enough to endanger the inexperienced, as a means to satisfy what I have latterly come to regard an infantile "look how cool I am, look what I can do" egotism.
I didn't need that. The junior devs I've helped with similar situations didn't need that. The devs I've worked with who are older and vastly more knowledgeable and capable than I am, but who are with good cause afraid that no one will ever hire them into another engineering role because they have wrinkles and lives and don't spend all their off hours dinking around with the latest frontend fad, really don't need that. And our field doesn't need that, either.