You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
29 lines
1.0 KiB
29 lines
1.0 KiB
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
|
|
|
|
|
|
|