Do Lots of Deliberate Practice

From WikiContent

(Difference between revisions)
Jump to: navigation, search
Current revision (09:42, 8 August 2009) (edit) (undo)
 
(11 intermediate revisions not shown.)
Line 1: Line 1:
-
What is deliberate practice? It is not simply performing a task. If you ask yourself "Why am I performing this task?" and your answer is simply "To complete the task," then you're not doing deliberate practice.
+
Deliberate practice is not simply performing a task. If you ask yourself "Why am I performing this task?" and your answer is "To complete the task," then you're not doing deliberate practice.
-
You do deliberate practice to improve your ability to perform a task. It's about skill and technique. Deliberate practice means repetition. It means performing the task with the aim of increasing mastery of one or more aspects of the task. It means repeating the repetition. Over and over again. Until you achieve your desired level of mastery. You do deliberate practice not to complete the task but to master the task.
+
You do deliberate practice to improve your ability to perform a task. It's about skill and technique. Deliberate practice means repetition. It means performing the task with the aim of increasing your mastery of one or more aspects of the task. It means repeating the repetition. Slowly, over and over again. Until you achieve your desired level of mastery. You do deliberate practice to master the task not to complete the task.
-
The princpal aim of deliberate practice is to improve your performance whereas the principal aim of paid development is to finish a product. They are not the same. Ask yourself, how much of your time do you spend
+
The principal aim of paid development is to finish a product whereas the principal aim of deliberate practice is to improve performance.
-
<blockquote>
+
They are not the same. Ask yourself, how much of your time do you spend
-
* Developing a product for someone else?
+
developing someone else's product? How much developing yourself?
-
* Developing yourself?
+
-
</blockquote>
+
-
How long does it take to acquire expertise?
+
How much deliberate practice does it take to acquire expertise?
<blockquote>
<blockquote>
* Peter Norvig [http://norvig.com/21-days.html writes] that "It may be that 10,000 hours [...] is the magic number."
* Peter Norvig [http://norvig.com/21-days.html writes] that "It may be that 10,000 hours [...] is the magic number."
Line 15: Line 13:
</blockquote>
</blockquote>
-
The expertise arrives gradually over time &mdash; not all at once in the 10,000th hour! Nevertheless, 10,000 hours is a lot: about 20 hours per week for 10 years. Given this level of commitment you might be worrying that you're just not expert material. You are. Greatness is largely a matter of conscious choice. ''Your'' choice. Research over the last two decades has shown the main factor in acquiring expertise is time spent in deliberate practice. Innate ability is ''not'' the main factor.
+
The expertise arrives gradually over time &mdash; not all at once in the 10,000th hour! Nevertheless, 10,000 hours is a lot: about 20 hours per week for 10 years. Given this level of commitment you might be worrying that you're just not expert material. You are. Greatness is largely a matter of conscious choice. ''Your'' choice. Research over the last two decades has shown the main factor in acquiring expertise is time spent doing deliberate practice. Innate ability is ''not'' the main factor.
<blockquote>
<blockquote>
* Mary: "There is broad consensus among researchers of expert performance that inborn talent does not account for much more than a threshold; you have to have a minimum amount of natural ability to get started in a sport or profession. After that, the people who excel are the ones who work the hardest."
* Mary: "There is broad consensus among researchers of expert performance that inborn talent does not account for much more than a threshold; you have to have a minimum amount of natural ability to get started in a sport or profession. After that, the people who excel are the ones who work the hardest."
</blockquote>
</blockquote>
-
There is little point deliberately practicing something you are already an expert at. Deliberate practice means selecting something you are ''not'' good at. Deliberate practice is about learning. About learning that changes you; that changes your behaviour.
+
There is little point deliberately practicing something you are already an expert at. Deliberate practice means practicing something you are ''not'' good at.
<blockquote>
<blockquote>
* Peter: "The key [to developing expertise] is ''deliberative'' practice: not just doing it again and again, but challenging yourself with a task that is just beyond your current ability, trying it, analyzing your performance while and after doing it, and correcting any mistakes."
* Peter: "The key [to developing expertise] is ''deliberative'' practice: not just doing it again and again, but challenging yourself with a task that is just beyond your current ability, trying it, analyzing your performance while and after doing it, and correcting any mistakes."
Line 26: Line 24:
</blockquote>
</blockquote>
 +
Deliberate practice is about learning.
 +
About learning that changes you; learning that changes your behaviour.
Good luck.
Good luck.

Current revision

Deliberate practice is not simply performing a task. If you ask yourself "Why am I performing this task?" and your answer is "To complete the task," then you're not doing deliberate practice.

You do deliberate practice to improve your ability to perform a task. It's about skill and technique. Deliberate practice means repetition. It means performing the task with the aim of increasing your mastery of one or more aspects of the task. It means repeating the repetition. Slowly, over and over again. Until you achieve your desired level of mastery. You do deliberate practice to master the task not to complete the task.

The principal aim of paid development is to finish a product whereas the principal aim of deliberate practice is to improve performance. They are not the same. Ask yourself, how much of your time do you spend developing someone else's product? How much developing yourself?

How much deliberate practice does it take to acquire expertise?

  • Peter Norvig writes that "It may be that 10,000 hours [...] is the magic number."
  • In Leading Lean Software Development Mary Poppendieck notes that "It takes elite performers a minimum of 10,000 hours of deliberate focused practice to become experts."

The expertise arrives gradually over time — not all at once in the 10,000th hour! Nevertheless, 10,000 hours is a lot: about 20 hours per week for 10 years. Given this level of commitment you might be worrying that you're just not expert material. You are. Greatness is largely a matter of conscious choice. Your choice. Research over the last two decades has shown the main factor in acquiring expertise is time spent doing deliberate practice. Innate ability is not the main factor.

  • Mary: "There is broad consensus among researchers of expert performance that inborn talent does not account for much more than a threshold; you have to have a minimum amount of natural ability to get started in a sport or profession. After that, the people who excel are the ones who work the hardest."

There is little point deliberately practicing something you are already an expert at. Deliberate practice means practicing something you are not good at.

  • Peter: "The key [to developing expertise] is deliberative practice: not just doing it again and again, but challenging yourself with a task that is just beyond your current ability, trying it, analyzing your performance while and after doing it, and correcting any mistakes."
  • Mary: "Deliberate practice does not mean doing what you are good at; it means challenging yourself, doing what you are not good at. So it's not necessarily fun."

Deliberate practice is about learning. About learning that changes you; learning that changes your behaviour. Good luck.


By Jon Jagger

This work is licensed under a Creative Commons Attribution 3

Back to 97 Things Every Programmer Should Know home page

Personal tools