From 89f641be1a2b7eac883b15b98100ca70c6c87e7c Mon Sep 17 00:00:00 2001 From: Mx Kookie Date: Mon, 21 Dec 2020 06:23:30 +0100 Subject: code dump --- infra/website/content/blog/xxx_timetracking.md | 29 ++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 infra/website/content/blog/xxx_timetracking.md (limited to 'infra/website/content/blog/xxx_timetracking.md') diff --git a/infra/website/content/blog/xxx_timetracking.md b/infra/website/content/blog/xxx_timetracking.md new file mode 100644 index 000000000000..1b5d7a605837 --- /dev/null +++ b/infra/website/content/blog/xxx_timetracking.md @@ -0,0 +1,29 @@ +Title: Bikeshedding time tracking tooling +Category: Blog +Date: 2020-12-16 +Tags: /dev/diary +Status: Draft + + +For the past year and a half or so I've been self employed as a +freelancer ([hire me] btw). Since then I've been confronted with the +question of time tracking. It's not something I generally did for my +personal projects, and while working for a consultancy, I usually had +access to some proprietary/enterprise tool running in the browser that +would allow me to track time done on different clients or projects. + +[hire me]: mailto:kookie@spacekookie.de + +I never quite liked the workflow of these tools however. For one, too +many things are in the browser for my taste, and secondly they often +made it difficult to see statistics, bulk edit entries, or deal with +entries with overlapping days (which is a problem when working late at +night, like I occasionally do). + +So I decided to write my own tool. Two drafts (one in Ruby, one in +Rust) later, enter: [cassiopeia], a plain text terminal time tracking +tool. + +[cassiopeia]: https://git.spacekookie.de + + -- cgit v1.2.3