Aiming for the ground, often missing

by Coranna Howard in Self

My projects are rather anomalous. There are few reasons they exist:

  1. I had a curiosity.
  2. I had a bucket full of spare time.
  3. I had a need for something (typically becoming generic).

That's essentially how it goes for everyone else, right? Right.

New projects involve a bunch of deliberation over design, which, I admit, becomes unhealthy somewhere around the umpteenth pass. Often, a project is left in some manner of limbo, or is never christened with a public shell (which usually comes down to how interesting I find it to be,1 regardless of how useful it is). I have learned much through horrible design (specifically: of realizing it after the fact) and I think it is good to fail, but I'm finding it more and more difficult to accept minuscule defects. My scrutiny core won't shutdown. I suspect the cause of this runs deeper than I'm willing to explore at present.

There are also, of course, the distractions. It is easy to get lost in the cornucopia of information that is the Internet.

While I'm here, I'll just get this out of my system: in August 2012 I received an email from a Google recruiter on a hunt. On the face of it, they were likely just flipping through GitHub users, searching for people to fill seats in their new offices, but I digress. The prospect is simultaneously appealing and terrifying. Part of me just wants to experience it, and another part is (very rightly so) screaming “unqualified”.

There are significant concerns here. For one, I'm very much the opposite of a web person. I hate web tech; I think it's all schizophrenic.2 Even if they're trying to fill a backend position, I'm still not the right person. I'm a sciolist, and I think that was recognized in the mock interview, seeing as they placed me in a pile and want to review my skills at some later date.

… I think they need to review their rules for probing GitHub.

However, since I have no other foreseeable future, I am somewhat aiming towards this end. If I don't end up with a job: no big deal. It would be a relief, really. And I will have learned a few good things. If I do end up with a job: a kind of validation, in a sense? I can just leave if it's not all it's chalked up to be (which I am highly suspicious about). Maybe this is all self-denial and it doesn't really take a master to fit in at Google. We shall see.

Side B: Goals for 2013

For one, I want to replace Jekyll, which I loathe greatly. I have a very primordial design in the works, but I haven't decided which charming language to use. It will probably be Go. Not Ruby.

Next on the agenda is to rebuild my log keeper, which is currently hobbled together with Gtk♯ (a notably fickle, possibly dead wrapper). There will be two components to this: a core library and a CLI application. At some point I want to introduce a distributed model.

In the same vein, I want to make a loose time tracker for Android — either to tie into my Hamster database, or to replace it entirely. I hope this does not turn into a Hamster port. Java makes me sad. Python does too, but not as effectively as Java.

Then there's the broker/load distributor/whatchamacallit. Basically, a library (and highly configurable application) for quickly slapping ØMQ schemes together. I'm not really sure why I started this, but it's a fun idea. It's also half-way done.

Lastly, I want to clean up and open-source my core game engine. I did a lot of backend work for an RPG – hardly a sane undertaking – that is probably useful to some crazy person somewhere.

There are a bunch of other things I'd like to do, but I won't boor this post with them.


  1. As you can probably imagine, I do not find many of them to be very interesting.
  2. Actually, I think tech is schizophrenic in general. Web tech is extra schizophrenic.