How To Be Fucking Awesome
gilesbowkett.blogspot.com
gilesbowkett.blogspot.com
In particular, this implies: "If you have not practiced, then you are not awesome."
So to be awesome at X, you need:
1) some natural talent for X, varies based on the field
2) a love for X that will allow you to practice for 10,000 hours
If you're having trouble finding discipline, the answer may lie in finding a way to love what you're doing more.
There is a lot of this in the startup community. I'm pretty sure the early life of Cisco is a pretty good example, but unsuccessful instances are all around you.
No. The trend in the research is that "natural talent" is a MYTH. It does not exist.
Agree or disagree, I don't care, but as a summary of my post, your comment is inaccurate.
Mugsy Bogues.
I could practice basketball for 10,000 hours, but there's no way I could do it professionally. You have to figure out what your natural abilities are, and work hard in those areas.
He was better than all the seven-feet-tall guys in that contest in 1986.
Assessing potential is hard. For example, one might assume that "height" is a phenotypical requirement for being an elite basketballer. But Webb proved that assumption is incorrect.
You'll likely make similar mistakes assessing your own potential. So why bother? Do what you love and let the chips fall where they may.
So yeah, let those chips fall where they may, unless they end up turning your life into shit.
PG's advice comes co mind: "Stay upwind". Playing basketball or the piano is not upwind, so it might be wise to forgo those things even if you love them.
If you're studying as a musician and targeting symphonic performance as a career goal, you need to realize that you're going into a field which maybe has a couple dozen job positions open up per year world wide. Being the 200th best clarinet player in the world, despite being statistically very impressive, means that you still won't be able to work as professional symphonic performer.
On the other hand, if you set that as a nice-to-have goal, but are fine working as a studio musician or teacher, it becomes a much more attainable goal.
Fortunately, as a software developer, even if you're only one of the top several thousand you have a pretty big chance of doing impressive stuff.
My sister is about to finish a degree in music from a decent conservatory, but I'm glad she decided to double major half-way through. She's very good, but she doesn't have what it takes to be competitive in a race for maybe a dozen open positions every year for her instrument.
The strawberry jam was awesome though:
He and his career constitute evidence that "height" is not a requirement to be an elite basketball player. It's definitional and not arguable.
In science today's "anomaly" is sometimes the evidence that leads to tomorrow's breakthrough.
It's just like when people say they shouldn't worry about monetizing because of Google.
Most tall people suck at basketball. Some elite basketball players are short. The fact that most elite basketball players are tall does not really help us write our basketball-success-prediction algorithm. People dedicate their careers to solving this problem. It is very hard.
Since this is hard and likely to yield garbage results anyway, and most likely only leads to worry, time-wasting and excuse-making don't bother with these thoughts. Instead, erase every doubt from your mind, get in the long boat, row west and find Valhalla. (Given Google somehow came up I had no choice but to bring Valhalla into the discussion.)
The right things don't exist... or have we already forgotten the whole "do what you love" concept?
What you do should be at the intersection of what you love and what you're good at.
Spend 20 hours each doing 10 different things, and then pick 2-3 of them to spend 200 hours doing. Then pick the one. While it may take 10,000 hours to be truly awesome, you can probably get a sense of being "good" at something in a much smaller amount of time.
The article gives Bill Gates as an example. According to the article, Gates is a great programmer because he sat in front of the computer for seven years. But Gladwell has it backwards... Gates sat in front of a computer for seven years because he had a passion for programming and that's what lead him to be great.
This has been brought up before: http://norvig.com/21-days.html
You /can/ be awesome with practice. But Bill Gates isn't an example. (And, yes, I know he wrote an early Basic interpreter, but he was also considered a mediocre programmer by many who knew him.)
I'm not trying to be snarky by pointing this out; I'm trying clarify that, while we should remember that in order to be great, we require dedication, effort and patience, the example chosen of Bill Gates shows that, sadly, this is often irrelevant.
If you did it full time (40 hours a week), you'll supposedly be fucking awesome in 4.8 years.
If this were true, I should be an awesome programmer. But I know I am not yet one. Far from it. So I call bullshit. (Some popular 'fucking awesome' programmers for reference: Steve Yegge, RMS, John Resig)
"A number of training studies in real life have compared the efficiency of practice durations rangingfrom 1-8 hr per day.These studiesshowessentiallyno benefit from durations exceeding 4 hr per day and reduced benefits from practice exceeding 2 hr (Welford, 1968; Woodworth & Schlosberg, 1954). Many studiesof the acquisition oftyping skill (Baddeley & Longman, 1978; Dvorak et al.. 1936) and other perceptual-motor skills (Henshaw& Holman, 1930) indicate that the effective duration of deliberate practice may be closer to 1hr perday." (K. Anders Ericsson)
projects.ict.usc.edu/itw/gel/EricssonDeliberatePracticePR93.pdf
After that time, my own thoughts start to elude capture, as if someone else's dream...
I can work longer, but I need to have a structured task - i.e. that doesn't require original thought, but is just a slog.
It's great to have a study to support my experience, and encourage me to value and nurture this "genius" time, with recovery time and activities.
EDIT at 1 hour per day, 10,000/365 = 27.4 years; say 30 years. If you are blessed with a naturally stronger constitution, enabling you to do 3 hours per day, you could do it in 10.
PS: If your in the top 5% of coders most people will consider you fucking awesome.
All I am saying is that may be 10,000 hours is not enough.
So while I am still closing in on those 10,000 hours it's going to take a lot more stretching for me to get there. There was plenty of time I could have spent getting better, but I have written ASM, high and low level networking code, Multi-threaded Apps, desktop apps, code parsers, scientific number crunchers, websites, and mostly I just wonder why other people find it hard.
I don't think of my self as Fucking Awesome but I do think I am close to that point.
365 days a year already includes 7 days a week. So you'd actually need 27.4 hours of practice a day to make it in a year.
Well, yeah, duh.
I think your assessment of what the book offers is actually more of an assessment of what Giles zeroed in on. I'm not defending the book--I have no interested since the concept can be summed up in a twitter post--but thought I'd point out that I think there's a different thesis at work.
You can summarize anything in a Twitter post: any concept, no matter how complex. Gladwell's advantage is that he tells really fascinating stories that explore his ideas in a real-world context.
I think that TDavis was trying to say was what I wanted to say, but he said it more concisely: this post wasn't really saying anything interesting. It was essentially saying "If you want to be fucking awesome, practice a lot." There wasn't very much more quantitative than that.
they make the same mistake here that everybody else makes with tagging. if you look at the research on tagging, the big tagging success story was delicious - which leveraged SELF-INTEREST in its tagging system and produced a useful public resource as an emergent byproduct. this is not coincidence! read James Surowiecki. seriously. economics 101 for social software.
leveraging independent self-interest is THE key factor which differentiates the wisdom of crowds from the stupidity of groupthink. "the wisdom of crowds" is really just a reiteration of adam smith's invisible hand. to create an invisible hand effect, you must leverage independent self-interest within a shared context where independent self-interested actions are visible to other independent self-interested agents.
every tagging system that fails to leverage self-interest fails to capture that. you can't just sprinkle magic web 2.0 fairy dust on something and go "Tagging!" if you want delicious results, you have to find out what made delicious work and emulate that. what made delicious work was a fundamental principle of economics. the reason so many sites have useless tags is that their makers are ignoring this fundamental principle. it's cargo cult site design.
similarly, this flagging nonsense flat-out ignores another basic fundamental of economics. what makes it even more insane is that Paul Graham already explained in one of his first blog posts about Bayesian filtering exactly why spam filters should be tuned to an individual's preferences and not to a group's. if you had a bunch of individually-tuned spam filters, you could find a way to leverage that. since you have a group-tuned spam filter, you have nothing but a tragedy of the commons magnet.
anyway, just ranting about why Hacker News should hurry up and cease to exist already.
edit: just for the record I'm responding to Reg's comment. I don't know if that's clear from the UI. it is a non sequitur rant, but it's not a complete non sequitur rant.
10000 -> 99.9% 1000 -> 99% 100 -> 90%
100 hrs is about 13 weeks (a quarter) of 3 uni 1hr credits + 1.5hr practice = 13 * 3 * (1 + 1.5)
if u take deliberate practice as vector, that's only the magnitude part
the direction part is what to study and that ends up being more important
given a constraint of 100 hrs, a nonprogrammer will end up becoming more productive studying lisp compared to java
but of course, to say such programmer is 90% better than average is too much :D ... and controversial
Perhaps this lifestyle precludes being "fucking awesome"?
What would be your definition of being "fucking awesome"?
In this case, the literal meaning of the phrase could be quite applicable, and well worth devoting 10,000 hours of deliberate practice to the cause.
Let me add: Don't waste your time reading books about trivial topics.
I am guessing programming "practice" would involve writing more ambitious programs? where would the feedback come from?
In the Ruby community we have the Ruby Quiz. I'm pretty sure that's copied from some other community, I think Perl. Every programming language community has practices of this nature.
It's absurd to suggest that deliberate practice has anything to do with body memory intrinsically. How many times will you write a regular expression in your life? There's no element of repetition there? The literature on deliberate practice cites Mozart, Bobby Fischer, and Bill Gates. Body memory has nothing to do with it.
The feedback comes from sharing with others, as in the Ruby Quiz, or benchmarking your code, or posting it on a blog. Another form of feedback would be seeing if your programs run at all. ;-)
Since no one actually made that claim - the intrinsically part that is - ..... :)
Is this one worth reading?