Low Skills Cause Procrastination
chestergrant.posterous.com
chestergrant.posterous.com
When I'm engaged, even if it's new territory, I'm on fire.
When I'm bored, it's painful to get through certain things, and it makes doing the dishes or laundry look appealing!
For most people, procrastination is a lack of will power to do that which we do not wish to do even though we know we must.
As an side, for just about all people, drugs like adderall and friends WILL help you be more productive, though it comes with its own consequences (lack of creativity in some, jitters, easily agitated, loss of apetite, etc.). And I do mean it would help just about anyone who took it, not just those diagnosed with ADD.
Avoidance is a well known coping mechanism. The author's reasoning is valid in that a person whose responsibility it is to solve problems, when facing a task that is beyond their skill level, will feel anxiety about delivering. In that scenario, avoidance is common. That is not to say that it is the only cause of procrastination.
Hence design strategies now tend towards ultra-gradual tutorialization with areas of instant gratification. Designs relying primarily on player discipline to master the content or make optimal decisions(notetaking, mapping, manual arithmetic) have all but disappeared, leaving those mechanics that allow success to feel intuitive and perpetually within reach.
Once basic mastery appears, something else happens: Players start willingly doing boring, tedious things in an effort to carve out the "last bits" of improvement. Micromanagement, speed-runs, grinding, statistical analysis, etc. The key thing is that these aspects only appear towards the back-end of the game's skill progression, after players already have confidence in prior technique.
And as it happens, the same is true of most technical endeavors - building on the fundamentals is how you grasp more complex stuff.
For me, there's usually a long period of "book study" where I nibble around the edges before I go in and attack a learning problem head-on with lots of practice. This process, though it has some caveats, lets me work from preexisting relationships more easily and adds "insurance" that I can retrieve value from all practice time.
One observation is that procrastinators are rarely delusional about what they (are not) doing. It's a genuine lack of willpower or a feeling of apathy. Neither of which are symptoms of low skill.
I don't think ignorance is the reason people have trouble writing Javascript. I think it's because writing Javascript for the web sucks. (I like node.js 1000x more than Javascript for the web. But it's the same programming language.)
They even changed their design. I'm surprised nobody talked about it.
The frequency at which MDN docs are linked in StackOverflow JavaScript answers shows that people are getting more familiar with them. PromoteJS took off recently and it has helped too.
- No offline version of the documentation.
- No distinction between Firefox-only features. (as others have mentioned)
- No mention of Chrome/Safari/IE-only features.
Are the MDN docs really seen as the 'canonical' reference to JavaScript or are they just the most accessible reference?
If you are interested in the official standards, please have a look at my other comment where I summarized them:
That isn't true. All important parts of what we call "Java Script" are well-defined at central, publicly accessible places.
However, one needs to know that the standardized part of Java Script is called ECMAScript, whose current version (5th edition) is available at:
http://www.ecma-international.org/publications/standards/Ecm...
One also needs to know that the DOM API is not specified by ECMA but by the W3C:
The DOM standard consists of 3 parts, all of which provide an appendix for ECMAScript:
http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/ecma-scri...
http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/ecma...
http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/ecma...
One might ask why all those JavaScript tutorials don't link to the standard, and why so many of them don't even mention the correct technical term "ECMAScript". No offense intended, but I guess they simply don't know any better. Although they ought to know.
For those who don't like to read technical standards, there are also nice secondary resources like the Mozilla Developer Network:
It's the browser idiosyncrasies which suck...
When something is easy you aren't stressed thus you aren't going to work on it immediately. When the issue becomes something stressful, because of time, that's when you begin working on it.
Therefore I'd have to say that we are pushed to work hard when we are stressed whether it's having low skills or having very little time.
I'd say when you are able to finish your project in a short amount of time, that shows you have a high level of skill, but if you have low skills and start it immediately and give the same results that shows a high level of skill in the form of determination.
Sometimes it is better to slow down and procrastinate rather than to hammer out something that just barely works. The creative part of the brain keeps working even if you're NOT actively thinking about the problem at hand.
If it is a genuinely difficult problem I've found that the most productive approach for me is to ensure I have all the facts in my head and then go and do something else completely unrelated. Usually some kind of solution will present itself at 3am or while I'm having a shower....
Of course, this approach doesn't work with all problems but it certainly beats hitting your head off a brick wall.
My other friend replied, "You say that like it's a bad thing."
Procrastination gets a bad rap. I think of it as "late-binding for ideas". Like late-binding in software there's some overhead and it's not always the best choice, but demonizing it is bullshit Protestant work ethic run amok.
If you've ever found yourself frantically slaving away at priority # 10392 while priority # 1 goes all to hell, and you're miserable because you know exactly what you're avoiding (and what it's costing you), you'll have some idea of why procrastination has an evil reputation.
I think your point is more that "be the labor great or small, do it well or not at all" is absolute crap advice. I'm absolutely agreed with you on that. There are also tasks that should be delayed, because they may change or even prove unnecessary if you put them off.
Procrastination, though... chronic procrastination (and a whole slew of psychological defenses that grew around the basic action paralysis) has pretty much destroyed my father's life, work, relationships, etc.. I've had my own issues, though I do a lot better now than in the past.
Another big reason however I've found is being in a state of "overwhelm", when you have a too large array of problems and tasks it can easily led to procrastination since the problem seems insurmountable. The only recipe for this I've found is to concentrate on a small aspect of the problem/solution and start there, then start on the next and so on
I sometimes think I'm using a specific skill, when I'm really using skills of learning that specific skill.
Once I've accepted the reality of my situation, the learning is enjoyable... even to the point of "relaxation/control/flow".