emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bingo <right.ho@gmail.com>
To: emacs-orgmode@gnu.org,
	Marcin Borkowski <mbork@mbork.pl>Org-Mode mailing list
	<emacs-orgmode@gnu.org>
Subject: Re: An Org-based productivity tool
Date: Thu, 11 Oct 2018 19:33:15 +0530	[thread overview]
Message-ID: <D7F3559B-DE40-4EAE-800C-F2F13EB856BC@gmail.com> (raw)
In-Reply-To: <87efcxaibq.fsf@mbork.pl>

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.

  parent reply	other threads:[~2018-10-11 14:03 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 [this message]
2018-10-11 14:57   ` Peter Neilson
2018-10-11 15:08     ` Ihor Radchenko
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=D7F3559B-DE40-4EAE-800C-F2F13EB856BC@gmail.com \
    --to=right.ho@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@mbork.pl \
    /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).