emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Dealing with growing backlog (was: next-error for agenda searches)
Date: Fri, 24 Dec 2021 22:51:03 +1100	[thread overview]
Message-ID: <87mtkqxlfm.fsf@gmail.com> (raw)
In-Reply-To: <87lf0ab6gg.fsf@localhost>


Ihor Radchenko <yantar92@gmail.com> writes:

> Samuel Wales <samologist@gmail.com> writes:
>
>> one issue with this great thing called capture is that there is
>> nothing quite so convenient that does the exact opposite.
>>
>> [you can regularly purge, if your life/forest is simple enough or you
>> have the physical ability to do things.  but you can't just
>> org-doneify-lower-value-stuff-i-captured-when-wasn't-sure-of-their-value-at-the-time
>> without adding energy, concentration, time, etc.]
>
> If I understand you correctly you are talking about ever-growing someday
> list.
>
> My latest solution to this problem (which I am quite happy with) is the
> following:
>
> 1. Every day/week I go through recently added someday staff and look if
>    it still looks useful.  For ideas, I just check if they still make
>    sense and for links, I open each link and skim through the abstract
>    and sometimes link text in more details.
>
>    When I first did the above, I was surprised that 50-80% of captured
>    staff is just gone because it is not as interesting as it looked
>    initially.
>
> 2. The ideas/links I mark for some day in future are scheduled using
>    org-learn. They will appear again in my agenda a few days later and I
>    can re-assess them. If still looks interesting, but someday not now -
>    reschedule using org-learn utilising spaced repetition. Otherwise -
>    archive.
>
>    With the above approach, I only see "not sure" ideas
>    days->weeks->years later. Only several times a year. More useful
>    ideas remind about themselves more frequently and I often end up
>    actually using them.
>
>    Credit of this idea:
>    https://www.getdnote.com/blog/how-i-built-personal-knowledge-base-for-myself/
>
> The total time needed to do the described is surprisingly small,
> especially with the ability to do bulk agenda operations to postpone all
> the maybe staff when you have no time/energy/mental power.
>

I use a very similar technique. Provided you do this type of
'house keeping" on a regular basis, it doesn't take long and the quality
of material in your knowledge base increases.

I've also learnt to be quite ruthless in making decisions about what to
archive and what to simply delete. This is possibly the hardest
behaviour to learn. In a digital age, it is way too easy to keep
everything. However, this has a hidden cost - the quality of material
degrades and results from searching etc become less productive because
there is too much 'noise' in your data. Data, like many other things,
degrades over time. It is important to learn how to recognise when
things have passed their 'use by date' and just get rid of them.

I'm often stunned by people who boast about the fact they still have all
their emails boing back to 1990 and are somewhat proud about having an
email archive with over 50Gb of messages. Reality is, the vast majority
of those email messages will never be read again and are of little or no
actual value.

Knowing when to just delete old data is almost as important as gathering
it, but a much harder skill to master.



  reply	other threads:[~2021-12-24 12:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15  1:34 next-error for agenda searches Samuel Wales
2021-12-18  8:44 ` Samuel Wales
2021-12-18 10:09   ` Ihor Radchenko
2021-12-19  1:10 ` Samuel Wales
2021-12-19  1:14   ` Samuel Wales
2021-12-19 13:31   ` Ihor Radchenko
2021-12-20  1:45     ` Samuel Wales
2021-12-20  1:58       ` Samuel Wales
2021-12-20  2:01         ` Samuel Wales
2021-12-20 14:57       ` Ihor Radchenko
2021-12-20 22:15         ` Samuel Wales
2021-12-20 22:16           ` Samuel Wales
2021-12-24  1:15             ` Samuel Wales
2021-12-24 11:14               ` Dealing with growing backlog (was: next-error for agenda searches) Ihor Radchenko
2021-12-24 11:51                 ` Tim Cross [this message]
2022-05-15  7:22                   ` Ihor Radchenko

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=87mtkqxlfm.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: Dealing with growing backlog (was: next-error for agenda searches)' \
    /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

Code repositories for project(s) associated with this 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).