Just_existing comments on Make your training useful - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (48)
This article made me think of a list I've been informally trying to make, of what stupidity feels like on the inside. The point is to identify when I'm writing code poorly - as the output will probably be even more bugridden than normal, and possibly the output is appropriate to debug-by-starting-over (Though starting over violates my normal policy.)
Stupidity feels like being bored, being in pain, being distracted, wanting to do anything else than this. Stupidity feels like being unworthy of these divine (external) ideas. Stupidity feels like blind plodding obedience. Stupidity feels like lovely and/or grotesque baroque clevernesses.
Trying to stop working and recover when I notice myself being stupid might be the right move, but I think pushing through it (aside from staying up late, which is a mistake) is a better policy. You have to learn to be productive on demand rather than when you're in the mood for it.
That sounds like a way to end up spending your in the mood for productivity time undoing the damage you do when you try to be productive on demand.
A while ago i started to motivate myself with good old conditioning. Every time I started to work on a project I ate an M&M. (I actually got the idea from the very first lecture from what will soon be the "Center of Modern Rationality" concerning the sunken cost fallacy.) This "technique" worked suprisingly well. After a while my subconciousness seemed to become a little less reluctant to start working. My "mod" was better. Could be a placebo effect of course, and could only work on myself, but its cost nothing to try. Let me know please if someone actually does.