18
Mar 11

WordPress Simple Graph Plugin

One of the downsides of working for IBM (and frankly, there aren’t that many), is that most of the work I do is usually under a pretty strict NDA. I’m learning a lot about the innards of database and High Availability and Disaster Recovery, but I can’t actually go blogging about it 🙁 However, IBM support a lot of open-source work and so they actually understand it (many companies I’ve worked for don’t). So long as you let your manager know what you’re working on and it isn’t something that competes with IBM products (fair enough, if I’m doing DB2 internals all day, I shouldn’t go work on MySQL internals on weekends for a dozen different reasons), then you can hack away on anything you want in your spare time.

That in mind, I’m finally getting back to some coding in my spare time (what little of it I have), and I’m starting slowly with some maintenance work on a WordPress Plugin called Simple Graph. You can see it in action over on my training blog, it’s what’s making the graph on the right of the page that tracks my weight:

Simple Graph sidebar widget

Simple Graph sidebar widget

It’s just a very simple widget for taking in hand-entered numerical data and plotting it dates.  The codebase has stagnated since 2007, so its author has given me permission to maintain it, and I have a list of things I want from it before I’ll call it done:

  • Clean commented code without any PHP warnings or notices
  • Fully WordPress 3.1 compatible
  • All options working as documented
  • Documentation updated to be more accurate and expansive
  • Better SQL query structure
  • More checking of input data
  • Multiple graphs working
  • Shorttag substitution in posts working

Once that’s done, I have a small list of features I want to add to it:

  • CSV import and export of data
  • Area graphs
  • More options to control graphics – line thickness, grids, background options, etc.
  • Use more GD features to give better looking end results
  • Use more Google Chart API features for better looking end results

Once that lot is done, we should be up to version 1.10 or thereabouts. I’ll post up a roadmap on the Simple Graph page I’m putting up later on. If you’re using the plugin and have any features you’d like to see, let me know using the comments below.

So far, I’m about a third of the way into cleaning up the code and commenting as I go. Feels good to finally be working on something for fun again..


17
Mar 11

Pycon 2011 videos

The Pycon 2011 talks were recorded and the videos are up here. Makes for interesting viewing, especially for those of us who can’t hop on a plane to Atlanta to attend a conference on a language we use for our side projects instead of our 9-to-5 work 😀


20
Jul 10

My interviews at Google

Google LogoSo I’ve now completed the interview process twice with Google (once in 2007 and once in 2010), and while I’m not sure advice from someone not hired after two run-throughs is all that useful, I figured that the more information out there for those undergoing pre-Google-Interview stress, the better, so here’s how it went.

In both cases, I was contacted out of the blue by a Google recruiter. The first time I had been considering looking for a new role and pursued it immediately; the second time I hadn’t been and put off the recruitment process for several months, during which the same recruiter contacted me again twice to follow up. If nothing else, that’s a nice ego boost, but a more cynical mind might be considering the shotgun approach to a narrow recruiting filter and commissions 😀

First, a quick data point, I was applying for an SRE(SA) position on both occasions – Site Reliability Engineer (System Administration), because in most of my roles to date, I’ve been doing both sysadmin and development work and I’ve never seemed to drift towards one pigeonhole or another. SRE(SA) seemed optimal – interesting sysadmin work on large-scale systems and quite a bit of tool-writing to boot. This was decided on between myself and the recruiter, based on the self-assessment form you are given to fill out. I would love to know how they get around illusory superiority and the Dunning-Kruger effect with those forms, especially given the wierd bias they’d have in the dataset from having so many of the best in their fields working there.

Both times, the process proceeded in the same way: Continue reading →