aboutsummaryrefslogtreecommitdiff
path: root/infra/website/content/blog/xxx_timetracking.md
blob: 1b5d7a605837ff220aed5c42b928c39d5a67fb0c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
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