rlp10 comments on My Algorithm for Beating Procrastination - LessWrong

81 Post author: lukeprog 10 February 2012 02:48AM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Article Navigation

Comments (138)
Tags: akrasia

Comments (138)

You are viewing a single comment's thread.

Comment author: rlp10 09 February 2012 12:05:30PM *  4 points [-]

So, for boot-strapping purposes (i.e. learning as you go), perhaps the algorithm would look like this?

Diagnosis

  • A1. Read about the four "factors" of procrastination (expectancy, value, impulsiveness and delay)
  • A2. Notice that you're procrastinating
  • A3. Consider which factor is most relevant
  • A4. Are you confident you have identified the most relevant factor?
  • If YES, go to A5
  • If NO, go to A1
  • A5. Considering your recorded results so far (if any), have you learned a subskill which can address the relevant factor?
  • If NO, goto B1
  • If YES, goto C1

Learning Subskills

  • B1. Read about the subskills relevant to the problem factor
  • B2. Choose the subskill that appears easiest for you to learn
  • B3. Make a plan to learn, implement and practice that subskill
  • Goto C1

Implementing Subskills

  • C1. Implement the relevant subskill
  • C2. Record the results of implementing the subskill
  • Goto A2 when relevant

What do you think?

Comment author: lukeprog 09 February 2012 06:19:39PM 0 points [-]

Yes, except that you want the algorithm to give you the opportunity to learn and implement more than one subskill.

Comment author: rlp10 10 February 2012 12:36:39AM *  0 points [-]

A5. Considering your recorded results so far (if any), have you learned a subskill which can address the relevant factor?

If NO, goto B1 (learning a new subskill)

If YES, goto C1 (implement an existing subskill)

My intention was that the algorithm would lead to your learning as many subskills as were necessary until the procrastination was beat, but no more.

Powered by Reddit Powered by Reddit