Git Data

A small analysis of the projects I work on and how I work on them. Most of these are public on my GitHub. Some caveats to remember...

• Commits do not strictly represent effort. A single commit can be one line or one thousand lines, and those lines could be autogenerated or painstakingly researched.
• I occasionally travel and I don't think these times represent that.
• Commits are only taken from the master branch.

That said, I can definitely see patterns, so let's go! Use the checkboxes to filter repos. For some context, I've can broadly categorize my projects into a few types:

• long term, non-Go: dotfiles, journal, www.bbkane.com - these are writing and configuration and grow with me over years (my dotfiles have been around a decade at this point)
• shorter term Go CLI tools - these are mostly CLI tools that I make feature complete and then just update dependencies on.
• the outlier is warg, which is 5 years old and written in Go. It's evolved over time because the afore-mentioned CLIs depend on it.

• If viewing on a phone, use the landscape orientation.
• I seem to have a pretty hard stop between 11PM - 5AM - sleeping is fun!
• My most-committed time is 9PM Saturday
• envelope was mostly written on Sunday evenings
• I mostly work during the weekends on these. Friday work is mostly due to inDays, and I'm very grateful LinkedIn let's me invest in myself one Friday a month.

• My dotfiles are 10 years old!
• I really up'd my commits when the COVID shutdown started.
• I tend to work on a project for a while and then move on - taggedmarks, then grabbit, then fling, starghaze, shovel, and envelope.
• I've put pretty consistent effort into dotfiles, journal, and warg over several years.

This table isn't that interesting to look at, but I keep it around for debugging the graphs.