Motivation

Why did I do this?

The Problem

I’m passionate about internal tooling. If I’m making software that will delight a paying client, I ought to be able to bring that same energy to my team to make their lives (and mine) easier.

I noticed one day that I had received over a hundred automated emails from Jira alone. Thanks to David Allen’s GTD, I’ve taken to simply acting on short tasks immediately. Most of our code reviews fall into that category and don’t take much time.

But the number of emails generated by Jira is just too much to handle: one per action by any reviewer. In our team, that amounts to an average of 5 per pull request, assuming nobody leaves any comments or comment Likes.

I wanted an inbox I didn’t need to remember to consult, and wrote Bittray as a response to that.

Learning New Technology

Bittray is written in Go and this documentarion site was produced using Jekyll, the Ruby static site generator.

I’ve been meaning to delve into Go for a while now. As a polyglot developer, I’m always eager to learn other patterns, paradigms, and add to my toolbox.

And as of 1.11, Go has a WASM build target, which is definitely interesting, even though the binaries go build currently produces are enormous.

Though I’m very comfortable with TravisCI, I also took this opportunity to integrate AppVeyor.

I also had a suggestion from a learned industry colleague to check out Azure Pipelines, which is on my to-do list.

Let’s be realistic

This is hardly revolutionary. It’s a tiny tool I wanted for myself that I am sharing with my colleagues. Being an open-source enthusiast, I’m also quite open to developing new features based on user requests.

Don’t be shy to file an issue.