Posts I've written on vacation or long plane flights

I’m developing a habit, it seems, of writing long, in-depth posts on some technical topic or other, while on long trans-Atlantic plane flights (the flight from London to LA is a real doozie). This also happens when I have long stretches of time near the ocean. These are those posts.

Setting up a Staticman server for comments on Jekyll and static sites

31 Dec 2017

I’m running Staticman for comments on this blog. If you’re using the main/public instance of the app, this requires you to add Staticman as a collaborator to your site repo, which I decided I’d rather not do… so I’ve run up my own instance of the application, and this is a quick look at how I did it.

» Read post

Setting up Staticman for comments on a Jekyll blog

21 Dec 2017
threaded comments as they appear on this website

Despite the fact that I’m not really a front-end dev, getting threading to look decent was not the hardest part of this.

I’ve been wanting to set up Staticman on this site for a while. I took a swing at it a year or so ago, but either because I was less experienced with working with webapps and I was insisting on running up my own instance, or because it’s in Node and I’m a Ruby dev primarily, or because ¯\_(ツ)_/¯, I couldn’t get it to work. I ended up adding Disqus to the site, but since they just got bought and I have no idea who the new owners are, I’ve finally gotten around to setting up Staticman. There is an excellent post on Made Mistakes about this that I’ve cribbed a lot from, but there were a couple of gotchas I ran into that took me a while to solve.

» Read post

Dokku: Backing up apps on Dokku

30 Jun 2017

Previously in the series, I’ve focused on setting up and using Dokku. This post is less Dokku focused, and more on making sure that you keep all the precious data you generate and collect with the apps on it safe.

» Read post

Dokku: Automated deployment to Dokku

23 Jun 2017

In the first two posts of the series, I looked at setting up Dokku and setting up automated builds and testing with Codeship, Code Climate, and Hakiri. This one ties those two together and covers the process I’m using for automated deployments with Dokku and Codeship (and the gotchas I hit along the way).

» Read post

Dokku: Automated Builds and Testing

16 Jun 2017

Last time in the Dokku series I went through how I set up Dokku on a VPS. This one is going to be about setting up Codeship, Code Climate and Hakiri (Ruby only, though the principles should be pretty similar for other languages/frameworks) to automate builds and testing. Should be a bit shorter, because there were fewer gotchas in this than in setting up Dokku (not that there were many there!)

» Read post

Dokku: Setting up Dokku

09 Jun 2017

Heya. I posted last week about building Url Grey, my URL shortener, a process which lead me to discovering and setting up some new tools. Specifically, Dokku, Codeship for Continuous integration and delivery, and Code Climate and Hakiri for code security, style, and test coverage reporting. I’ve decided to write the whole process up more completely, in part for myself, and in part because there a few hiccoughs I ran into that didn’t have answers (or readily apparent answers–it took me some hunting and piecing together of things) online.

This will be part of a series (hello slug up above!), starting with setting up Dokku, and moving on through the process of linking all the pieces together to get a continuous deployment setup.

» Read post

assert practice_tdd, joyful

11 Apr 2017

A parable told in code.

class Rubyist < Human
  include EmotionalAccessors
  include RelationshipToTDD

  attr_reader :tdd, :experience, :joy, :worry_about_others_perception

  def initialize
    @worry_about_others_perception = 10 # or so I'm told
    @experience = 2 # years, on average?
    @joy = 0 # cannot be inferred without more data



class RubyN00b < Rubyist

  def initialize
    @worry_about_others_perception += 500
    @experience = 0
    @tdd = false



» Read post