emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: Matt Lundin <mdl@imapmail.org>, Org-mode Mode <emacs-orgmode@gnu.org>
Subject: Re: Re: Added support for "habit tracking"
Date: Fri, 23 Oct 2009 21:20:13 -0400	[thread overview]
Message-ID: <B6B7FB6B-FD59-4F31-9EA0-E2FF9F737242@gmail.com> (raw)
In-Reply-To: <1e5bcefd0910230824i820e70fsc4ff24b9978f069c@mail.gmail.com>

On Oct 23, 2009, at 11:24 AM, Marcelo de Moraes Serpa wrote:

> But isn't consistency in the long-run the fact that you have  
> actually *completed* them?

Yes and no.  I don't need to always complete them, and yet I could  
still be consistent.  It's optimal to be perfectly consistent, but  
that's no what's expected.

Missing a deadline is something else entirely, as one imagines there  
are consequences.  Missing a habit is, well, just harder to pin down.

> In this case, IMO, a weekly review is a habit, even though it does  
> not happen daily, it still has consistent period to be respected (1  
> day, every seven days), and a deadline (the very same day). Or  
> habits need to be daily?

I guess it all comes down to whether you just want the graph or not.   
A weekly review is really something you need to do every week, so it's  
just a repeating task.  I have too have regular repeating tasks for  
things like downloading bank statements, paying the rent, visiting the  
dentist, etc.  These are tasks which are _each important in  
themselves_.  A habit, on the other hand, is never important in  
itself.  It doesn't matter so much if I miss washing the dishes  
today.  It's the _habit overall which is important_.  As long as I  
wash them more often than not, I'm doing better than if I'd never used  
Org at all.

The only difference between regular repeating tasks and habits is this:

  1. Habits appear at the bottom of the agenda (by default)
  2. Habits can be removed by hitting K
  3. Habits have a little graph, since you need to see consistency  
over a
     period of time.

Another difference between habits and tasks is this: If I get to the  
end of my day and there are tasks yet undone, it means I need to  
schedule them for another day.  But if there are habits undone, *I  
never reschedule them*.  Once I reach a point during the day when I  
know I no longer have time or opportunity to work on my habits, I just  
hit K and exclude them from the view.  What it means is that I'll try  
again to do them tomorrow.

But since tasks are, in a way, much more self-important, they need to  
be allocated to a certain day, or given a specific deadline -- whether  
or not that deadline repeats itself.

John

  reply	other threads:[~2009-10-24  1:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19  8:26 Added support for "habit tracking" John Wiegley
2009-10-19  8:28 ` John Wiegley
2009-10-20 14:02 ` Matt Lundin
2009-10-20 15:29   ` Carsten Dominik
2009-10-20 15:56     ` Matthew Lundin
2009-10-20 16:55     ` John Wiegley
2009-10-20 17:13       ` Marcelo de Moraes Serpa
2009-10-20 17:19         ` John Wiegley
2009-10-20 18:20           ` Marcelo de Moraes Serpa
2009-10-20 16:48   ` John Wiegley
2009-10-20 17:11     ` Matthew Lundin
2009-10-20 18:30     ` Samuel Wales
2009-10-20 18:38       ` Marcelo de Moraes Serpa
2009-10-20 18:48         ` John Wiegley
2009-10-20 18:48       ` John Wiegley
2009-10-20 18:52 ` Sven Bretfeld
2009-10-20 18:56   ` Sven Bretfeld
2009-10-20 19:06     ` Carsten Dominik
2009-10-20 19:36       ` John Wiegley
2009-10-20 21:22         ` Marcelo de Moraes Serpa
2009-10-21  6:36         ` Carsten Dominik
2009-10-21 18:36         ` Matt Lundin
2009-10-21 22:40           ` John Wiegley
2009-10-23  6:10             ` Marcelo de Moraes Serpa
2009-10-23 10:34               ` John Wiegley
2009-10-23 15:24                 ` Marcelo de Moraes Serpa
2009-10-24  1:20                   ` John Wiegley [this message]
2009-10-24 12:55                     ` Matthew Lundin
2009-10-24 14:36                       ` Matthew Lundin
2009-10-25 12:26 ` Paul Mead
2009-10-25 12:37   ` Carsten Dominik
2009-10-25 12:50     ` Paul Mead
2009-10-25 12:38   ` Paul Mead

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=B6B7FB6B-FD59-4F31-9EA0-E2FF9F737242@gmail.com \
    --to=jwiegley@gmail.com \
    --cc=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \
    /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).