There’s no doubt in my mind that journalling is a really useful thing to do, both for personal logging and keeping track of progress and decisions at work. I’ve spent a bit of time experimenting, and I’ve tried various logging and journalling apps, including Quiver, Ulysses, rolling my own using vim and one of the most popular Mac Journalling apps, Day One. All of these have pros and cons, and for various reasons I can never settle into sticking to just one methodology, so I’m currently using Day One for personal logging, helped along by Slogger (mentioned previously in my post on Mac Dev Tools).
Here’s a script which prints a sorted list of the files in a git repository, but sorted by when their last commit occurred, rather than the standard modification, creation or access times you’d see from ls. This will form the bases of another script in future, which will give me a list of files that haven’t been updated in git for a certain amount of time, but I think this might be useful as-is to some people.
Launchbar actions for browsing Pinboard are pretty much covered, but I couldn't find any actions to save them in the way I want, so set about writing my own. This post covers my mini AppleScript adventure using Launchbar 6's cool Action Editor.
This isn’t strictly a reading list, because it’s about books I’ve already read, but it’s a list of reading! As part of my effort to more regularly blog this year I’ve found myself straying from purely techy topics into the realms of the more personal, and as part of that I’ve been covering one of my most favourite things in the world. Music. This was originally a back-burner topic, but then when I wrote my 2015 Roundup I enjoyed it, so I’ve decided to make it regular.
In February 2015 I discovered a cross-site scripting vulnerability in Ubiquiti’s EdgeRouter Administrative interface. These are powerful and cheap devices which are also pretty fun to use and configure, so I’d definitely recommend them even though I found this issue. After a couple of false-starts and emails getting lost I was invited to submit details of the vulnerability via HackerOne, and they fairly quickly decided to pay me a $500 US bounty.