From: Marcin Borkowski <mbork@mbork.pl>
To: Jean Louis <bugs@gnu.support>
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: Sun, 22 Nov 2020 22:28:01 +0100 [thread overview]
Message-ID: <875z5xgjz2.fsf@mbork.pl> (raw)
In-Reply-To: <X7qrBV/5VqG7My4Z@protected.rcdrun.com>
On 2020-11-22, at 19:16, Jean Louis <bugs@gnu.support> wrote:
> * Kristian Grönberg <kristian@gronberg.org> [2020-11-22 08:56]:
>>
>> > On 20 Nov 2020, at 10:23, Leo Okawa Ericson <leo@relevant-information.com> wrote:
>> >
>> >
>> > Some time ago I hacked together a bunch of elisp to create a clock
>> > table
>
> I am sorry what is clock table?
>
> [snip]
Well, and how is all that helpful at all?
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?)
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.
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2020-11-22 21:28 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 [this message]
2020-11-22 22:11 ` Jean Louis
-- 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:
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=875z5xgjz2.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=kristian@gronberg.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).