• Fun With Google Code Search

    So, today, one of my “friends” at work was so kind as to post a Google code search, with my name as a search term, on our internal IRC server (thanks a lot, Jeremy… jerk!). For those not aware, Google now has a specialized search engine that allows one to search through publically available source code (the bits that comprise the blueprint for a piece of software). It’s pretty handy for many things (computing various code metrics, finding interesting code snippets, and so forth). But, as it happens, it’s also a great way to find code authored by specific people. And, in this case, that specific person was me.

    Well, this got me thinking: Imagine you’re applying for a job. Further, suppose, in your younger, less experienced years, you made some of your work available online. Perhaps you contributed to some open source project. Or maybe you released something of your own. Well, your potential employer now has a very easy way to find these bits and bobs, and may very well choose to include them as part of your evaluation. Now, that’s fine if all you’ve ever made available online is top-quality code. But for hacks like me, this can be a problem.

    Of course, since the advent of the search engine, an employer has always had the option of digging around on the Internet for information about prospective employees, which is why it’s important to be careful about what you post online. But, for those in the tech sector, Google code search means their past work can now be more easily tracked down and evaluated.

    And in case you were curious, you can see what Google has to say about me here.

  • One Down

    Sure, it may be a small milestone, but my first piece of (very) short fiction is now complete! Or, at least, the very first, very rough draft is complete. At a little over 8800 words, or nearly 12 pages, it is, I think, the longest bit of creative writing I’ve ever put together. Yeah, I know, that’s not very big (a novella ranges between ~17,000 and ~40,000 words, though technically, it apparently qualifies as a Novelette), especially considering I expect to cut a good 800 words out during the rewrite phase, but given that it’s my first serious crack at creative writing, I’m pretty happy with it, despite the distinct lack of originality it represents (who needs originality, anyway, I ask you?).

    So now what? Simple: it goes in the vault. The idea, here, is that once a piece is complete, you set it aside for a while in order to gain some distance from it. Then, when you go back to edit the thing, you can do so with a fresh perspective on the work. And once the rewrite is complete, only then do you kick your baby out of the nest, hoping against hope that it’ll flap it’s wings a little and avoid crashing and burning too badly.

    Meanwhile, tomorrow I’ll get started on my next idea. It’s been rolling around in the back of my mind for the last week, so I’m kind of excited to pull it out of the cellar that is my hindbrain and see what it looks like in the light of day. Hopefully it ain’t too ugly…