1. While the page is loading, look at the utm_source crap in the URL and wonder why the submitter couldn't be bothered to clean that up.
2. Read the first sentence and identify this as a writer of the "I should start with a personal anecdote to make people like me" school of writing (a US thing? not sure), and start skimming for the actual content.
3. Slow down when the "Anders Ericsson" anchor appears, and wait for the mandatory "10,000 hours" reference.
4. Skim the six points, and realize that there's nothing new here -- you've read the same article before, only written by someone else.
(yeah, yeah, I'll log off now.)
1. Decide to read comments before the article.
2. Read your comment.
3. Decide I don't need to read this again.
4. Decide to leave a thank you before going elsewhere.
Thank you for your informative summary.
1. Read article, throw up.
2. Read comments, then realize that the comments made this substandard post worthwhile.
3. Upvote many comments.
4. Return to regularly scheduled programming.
-Innate talent > Practice. Painful to admit, but better if you can own up to your weaknesses early on and focus things you are better at.
-Extensive practice only applies to single tasks, not complex activities such as business which requires being good at multiple disciplines plus coordinating and understanding the interaction between those disciplines
I'd love to run a split-test of all bullets no header vs. current format - would be informative, maybe will try in one of my own blog posts . . .
The Key to Being Excellent at Skimming has an arrow pointing down.