I’ve recently added several services to my hobby VPS, including GitLab, Neo4J, and some custom-written Python stuff. I figured that it would become necessary for someone not logged in to the server to see the status of these particular processes, possibly for external monitoring purposes.

I recently had to upgrade a PostGIS-enabled PostgreSQL 9.3 database to 9.4. In the process, it was decided that the server itself should be rebuilt and expanded. I accomplished the upgrade by dumping the data from the 9.3 installation (with pg_dumpall -c), transferring the file over SCP, and loading it into the new database with psql.

Unfortunately that wasn’t enough - psql kicked back an error:

I wrote this short paper for a philosophy of computing course here at OSU.

I’ve been working heavily with Git, and the more I get into it, the more well-designed I find it to be.

I have run a Minecraft server for a couple of years now for my family and friends. The way it’s entertained me has changed over that time - first I was interested in the game itself, but I gradually became interested in how different rules and levels of enforcement affected gameplay.

But that’s a different story; I’m here today to talk about GPL violations.

The shellshock bug, though it’s now old news, is a bit more serious than how we treat it.

Last fall, I went to Startup Weekend here in Columbus, courtesy of the NEWPATH technical entrepreneurship group here on campus. It was a lot of hustle and a lot of fun.

I’ve been putting it off for a while now, but I axed my Facebook profile.

This past spring I had the good fortune of attending BoilerMake on the dime of my wonderful university.

Liquory is a webapp that I worked on over the course of a week and a half this summer with Claudius Mbemba. We produced it for the Delivery.com App Challenge.