rlp10 comments on My Algorithm for Beating Procrastination

[rlp10]

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?

[lukeprog]

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

[rlp10]

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.