emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org, "Sébastien Gendre" <seb@k-7.ch>
Subject: Re: How do you manage complex project with Org-mode
Date: Sun, 20 Mar 2022 13:16:52 +0800	[thread overview]
Message-ID: <87tubtdwzf.fsf@localhost> (raw)
In-Reply-To: <87zgm8ov7y.fsf@gmail.com>

Tim Cross <theophilusx@gmail.com> writes:

> For example, I
> would not have a task which says to review my tasks twice a week. Do you
> really need a task to remind you to do this twice a week? Do you really
> need to track that you have done this? I would classify such tasks as
> 'noise' tasks. They really don't perform any real purpose.  It is
> similar to brain dead project policies which state things like "every
> function must have a unit test". Many functions don't need a unit test
> and forcing people to write pointless unit tests does more damage than
> not having them.

I disagree about this specific example (not with your whole idea).
Reviewing tasks is important for people who can easily fall into
continuous routine. Dedicating several hours per week to look into what
you are doing in a broader perspective is valuable.

Note that I do not mean "review" as looking through _all_ the tasks.
Rather looking into current projects and deciding what to do, and, more
importantly, what not to do in the coming week/days/months.

See https://www.benkuhn.net/weekly/


  reply	other threads:[~2022-03-20  5:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  1:43 Sébastien Gendre
2022-03-01  4:03 ` Matt
2022-03-02 19:44   ` Sébastien Gendre
2022-03-01  6:43 ` Dr. Arne Babenhauserheide
2022-03-02 20:00   ` Sébastien Gendre
2022-03-01  7:12 ` Tim Cross
2022-03-02 20:33   ` Sébastien Gendre
2022-03-02 21:55     ` Tim Cross
2022-03-20  5:16       ` Ihor Radchenko [this message]
2022-03-20 21:24         ` Tim Cross
2022-03-21  9:25           ` Ihor Radchenko
2022-03-20  5:06     ` Ihor Radchenko
2022-03-01 19:26 ` Antonio Carlos Padoan Junior
2022-03-02 20:53   ` Sébastien Gendre
2022-03-01 21:06 ` Milan Zamazal
2022-03-02 20:58   ` Sébastien Gendre
2022-03-02 16:29 ` Quiliro Ordóñez
2022-03-02 21:05   ` Sébastien Gendre
2022-03-01  4:38 Eric Abrahamsen
2022-03-02 21:26 ` Sébastien Gendre
2022-03-02 23:35   ` Eric Abrahamsen

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:

  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=87tubtdwzf.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=seb@k-7.ch \
    --cc=theophilusx@gmail.com \


* 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


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).