emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: "Org-Mode Emacs" <emacs-orgmode@gnu.org>,
	"Kristian Grönberg" <kristian@gronberg.org>
Subject: Re: Clock tables and two ways to categorize tasks
Date: Mon, 23 Nov 2020 01:11:52 +0300	[thread overview]
Message-ID: <X7riKMZtlgwRxsit@protected.rcdrun.com> (raw)
In-Reply-To: <875z5xgjz2.fsf@mbork.pl>

* Marcin Borkowski <mbork@mbork.pl> [2020-11-23 00:28]:
> Of course, in an ideal world we'd be paid for the results, not for the
> time.  But:
> 1. Welcome to the reality, this is not an ideal world.  I am being paid
> for my time.  (And sometimes we really do not have a better option.  How
> would you calculate a teacher's wage?)

Yes sure. In that time many valuable things take place. But time is
more or less fixed per week or per month and is never as accurate.

Do you track that time of work with Emacs?

> 2. Clocking in and out is the question of habit.  It does not really
> take up a significant portion of my attention, especially with Ivy and
> org-mru.  I've been doing it for years, and while I do sometimes forget
> about it, an occasional error does not make the whole data useless.

> 3. Knowing where my time goes is the first step in optimizing it.

OK so you observe when doing task A how long time you spend in task A,
so that after 100 tasks you can find out where you spent most of time.

The tasks I create are normally delegated to others on distance and I
could not possible see what they do and how, if they really work or
not so time tracking would be inaccurate statistics. By observation is
found where most time is spent for nothing (useless dwelling).

  reply	other threads:[~2020-11-23  7:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 12:25 Clock tables and two ways to categorize tasks Marcin Borkowski
2020-11-19 14:47 ` Mikhail Skorzhisnkii
2020-11-19 14:52 ` Tim Cross
2020-11-20  8:20 ` Leo Okawa Ericson
2020-11-22  5:55   ` Kristian Grönberg
2020-11-22  7:06     ` Tim Cross
2020-11-22 18:16     ` Jean Louis
2020-11-22 21:28       ` Marcin Borkowski
2020-11-22 22:11         ` Jean Louis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-20  0:37 Bala Ramadurai

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=X7riKMZtlgwRxsit@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=emacs-orgmode@gnu.org \
    --cc=kristian@gronberg.org \
    --cc=mbork@mbork.pl \


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