One of the things you'll often hear as a programmer is that to be successful, you need to be constantly learning. Sometimes that's learning about a new technology, or learning a technology you use more in depth. It feels to me that this is getting harder and harder - there are always more frameworks, more programming languages, more tools to learn. Keeping up is difficult, especially if you have other people or things that demand your time. I have a little trick I've been using for some time, and I'd like to share my secret with you, dear reader. I call it lazily evaluated learning.Read More…
Posted on 2018-03-03
Just over two weeks ago, RokkinCat conducted their 14th Hack & Tell. Since I wasn't able to participate last October, I was eager to spend some time working on some project ideas I've been thinking about! This time, I didn't have a single strong idea - instead, I spent my time playing around writing extensions for Firefox using the new(ish) WebExtensions API.Read More…
Posted on 2018-02-13
Last night, I was musing about personal projects I undertook in 2017, and I realized that of the two big ones that I made, I didn't know if I could judge either as a success.Read More…
Posted on 2018-01-11
Once again, I found myself participating in a Milwaukee Hack 'n' Tell, organized by RokkinCat and conducted at Ward 4. I wrote some notes on how the day went in my dev journal, so I thought I'd share the experience here!Read More…
Posted on 2017-02-01
One of my favorite tools in the git tool suite is
git-bisect. For those of
you unfamiliar with it,
git-bisect is a sort of magical program that you
can use to quickly find which commit introduced a problem into a repository.
It does this by checking out commits in your repository's history, and you tell
it whether the state of the commits for whatever you're testing is good or bad.
It minimizes the number of times you need to do this by using a binary search
algorithm. Futhermore, if you have an automated test suite, you can tell
git-bisect to run the tests on your behalf (using
git bisect run) and
drive the whole process by itself. It has proven very useful to me over the
years, both in open source and commercial work.
Posted on 2016-11-15