emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Peter Neilson <neilson@windstream.net>, emacs-orgmode@gnu.org
Subject: Re: An Org-based productivity tool
Date: Thu, 11 Oct 2018 23:08:26 +0800	[thread overview]
Message-ID: <87bm80bjx1.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <op.zqp6ihpurns8nc@odin>

[-- Attachment #1: Type: text/plain, Size: 3057 bytes --]

Well, you could associate a reward to that kind of tasks.
For example, you can allow yourself to work half a day.

Alternatively, you can make a task you would like to do (say, watch a
new movie) to be blocked until the unwanted task is done.

"Peter Neilson" <neilson@windstream.net> writes:

> On Thu, 11 Oct 2018 10:03:15 -0400, Bingo <right.ho@gmail.com> wrote:
>
>> Le 10 octobre 2018 21:45:53 GMT+05:30, Marcin Borkowski <mbork@mbork.pl>  
>> a écrit :
>>
>>>
>>> - a warning when my efficiency is lower than a set value, and info
>>> about
>>>  how much work I need to do to bump it up to that value.
>>>
>>
>> Nice, but it has an anti-feature.  For procrastinators, warnings  
>> frequently have negative effects. It can be understood in multiple ways :
>>
>> 1. "What the hell" effect : As Dr Art Marckman tells in the book "Smart  
>> Change" , there is a "what the hell" effect where the victim goofs off  
>> even more to the extent of giving up a goal if he realizes that he is  
>> falling behind schedule, or has goofed off more than was advisable. The  
>> solution is to forgive oneself, and not beat oneself up. This warning  
>> looks like beating oneself up.
>>
>> 2. Showing how much work needs to be done to catch up goes against some  
>> self improvement philosophies. E.g. dividing work into subtasks helps in  
>> not getting overwhelmed by the amount of work.  Or the recommendation to  
>> plan breaks in addition to planning to slog, otherwise the plan to slog  
>> becomes overwhelming and procrastinators give up.
>>
>> Of course, if it works for you, go for it.
>
> Sabotage of the TODO list ...
>
> Managing the flow of my own work sometimes runs into unintended sabotage,  
> perpetrated by others or by me. The offending tasks are often large,  
> incapable of division, and not immediately crucial. For example, somewhere  
> in the middle of my list of "Get it done some other time, but not now,"  
> tasks is this one: "Repair the International 454 tractor."  It rests  
> comfortably on that list unless I either (1) need to use that tractor, or  
> (2) hear my wife telling me, "Why don't you ever get the 454 running? You  
> never get anything done around here! I need to use its bucket, and the  
> Mahindra doesn't have one." From that point onward, and my "TODO" thoughts  
> about writing, about programming, or about training horses are derailed.  
> In case (1) I need to figure out some other approach, like maybe using the  
> Mahindra. In case (2) my wife is right--as always--and my tendency is to  
> stop doing anything at all.
>
> My org mode TODO list is absolutely no help when I encounter one of these  
> show-stoppers. If anything, the list is an additional albatross adding to  
> my already encroaching depression.
>
> Maybe I need a brain-wave detector, connecting through emacs-lisp AI code  
> to a huge Pomodoro-style graphic display, that will alert me when I am  
> goofing off, falling asleep, or practicing mental evasion.
>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-10-11 15:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 16:15 An Org-based productivity tool Marcin Borkowski
2018-10-10 16:50 ` William Denton
2018-10-10 20:10   ` Marcin Borkowski
2018-10-10 20:45     ` Samuel Wales
2018-10-11 13:16       ` Roland Everaert
2018-10-11 13:25         ` Ihor Radchenko
2018-10-11 13:44           ` Roland Everaert
2018-10-11 13:56             ` Ihor Radchenko
2018-10-11 20:05         ` Samuel Wales
2018-10-11 20:05           ` Samuel Wales
2018-10-14  8:08       ` Marcin Borkowski
2018-10-16 21:04         ` Samuel Wales
2018-10-29  9:05           ` Marcin Borkowski
2018-10-11  8:58 ` Ihor Radchenko
2018-10-14  8:22   ` Marcin Borkowski
2018-10-11 14:03 ` Bingo
2018-10-11 14:57   ` Peter Neilson
2018-10-11 15:08     ` Ihor Radchenko [this message]
2018-10-14  8:19       ` Marcin Borkowski
2018-10-14  8:19     ` Marcin Borkowski
2018-10-27  7:38     ` stardiviner
2018-10-28  1:24       ` Samuel Wales
2018-10-29  9:19         ` Marcin Borkowski
2018-10-29 21:03           ` Samuel Wales
2018-10-14  8:15   ` Marcin Borkowski
2018-10-16 20:39 ` Adam Porter
2018-10-16 21:43   ` Sacha Chua
2018-10-27  7:41     ` stardiviner
2018-10-29  9:17     ` Marcin Borkowski
2018-10-29 12:31       ` Sacha Chua
2018-10-29 17:17         ` Marcin Borkowski
2018-10-25  9:45 ` Ihor Radchenko
2018-10-29  9:08   ` Marcin Borkowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bm80bjx1.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=neilson@windstream.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).