Right now I should be grading or preparing for classes, but honestly I’m three blog posts behind where I wanted to be by now (I haven’t forgotten my WisCon promise to make a post about tabletop roleplaying games) and fighting a pretty nasty headache. So what if I take a…
TLDR: I took two classes this semester, and I’m going to teach at least one, probably 1.5, classes next semester. I’m super psyched about it. I’ll still work for the library where I’m an adjunct, too, but fewer hours per week. I’m still available for full-time hire, if you have data for me to work with.
Pittsburgh’s Code & Supply just held a huge (1500 people) conference over the last three days, and of course I’d signed up to attend months ago, because 1) local 2) affordable 3) tech conference 4) with a code of conduct they seemed serious about. Plus, “Abstractions” is a really cool…
“We’ve got a pipeline problem, so let’s build a better pipeline.” –Bess Sadler, Code4Lib 2014 Conference (the link goes to the video) I’ve been thinking hard (for two years, judging by the draft date on this post) about how to grow as a programmer, when one is also a librarian.…
This is my tableflip post. I promised to write one, so here it is. It’s not very salacious, honestly.
I think there are two keys to why I was a successful electrical engineer, when I did not (initially) succeed as a computer scientist—despite being more interested in the latter, to begin with, and despite wanting to pursue the latter now. The first key: invisible struggle, no displays of fallibility…
I thought about writing a really long post about handling Unicode in Python, but, honestly, you should go watch this video; that’s where most of my points would have come from, anyway. (It’s a great video! It’s funny and helpful and relevant, whether you use Python 2 or 3. I…
I had the opportunity, at work (and a bit outside of work), to learn the GitHub API, as wrapped by Python’s github3 module. I found the documentation really hard to follow, maybe because I don’t have a lot of experience reading API docs, or because it wasn’t organized in the…
I had hoped to document all of the stuff I was learning each day, or at least each couple of days, through my first few weeks in this job. I knew I’d have a lot to share. But I’m so tired at the end of each day that I don’t really have a blog post in me. I hear one gets used to non-stop thinking for 8+ hours per day and functions better over time. :)
I’ve been rolling this post around in my head for a couple of days, in between attending conference and binge-(re)watching Firefly. It turns out, I have put a lot of time and effort—and, more importantly, thought—into creating and running a WiT group, so I have a lot to say…
