My first full day back at consulting after a month-long vacation, and it felt great. I started digging into the REST API for the system we were using, and I figured out how to build a simple command-line client to get data. I’d built a similar community analysis tool while at IBM, and that one saved lots of people hours and hours of work. Since we were starting to need similar reports, it made sense to build a tool instead of manually crunching the numbers. This time,
I decided to build the tool using Ruby instead of Java, packaging it into an .exe with Ocra. I found Ruby to be much easier to write in. The interactive mode made it easy to prototype my ideas. Gems meant that I didn’t have to hunt all over for packages and figure out how to make them work together. It was fun to come up with more ideas and add them to the tool.
I love making tools. I like digging into the wires behind web-based services and making up new ways to use stuff. The value isn’t as visible or as easy to appreciate as, say, web design work, but it’s much easier to build something quick and then tweak it to fit specific people. I like that part a lot – tailoring tools to specific ways of working.
I was thinking about the different things I might like to be really, really good at in twenty years’ time. My current shortlist: writing, drawing (mostly sketchnotes), and toolmaking. I think writing and drawing are like toolmaking for me too. They’re about making tools for the mind, helping people learn faster or more effectively or about more things. =) Maybe if I practise and learn more about writing and drawing — the way I’ve spent most of my life programming — I’ll be able to make wonderful little things too.