aboutsummaryrefslogtreecommitdiff
path: root/infra/website/content/blog/xxx_timetracking.md
diff options
context:
space:
mode:
Diffstat (limited to 'infra/website/content/blog/xxx_timetracking.md')
-rw-r--r--infra/website/content/blog/xxx_timetracking.md29
1 files changed, 29 insertions, 0 deletions
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
+
+