New Tools

Okay, I just placed the order for my next Timbuk2 bag. It's the new-fangled Laptop Messenger, with rubbery laptop sleeve and napoleon pocket. Size small, because I'm finding the iPad is just fine as my bring-to-work personal machine.

I need some other tools too. I need another swiss-army language. Back in the day this was Perl (before that it was Hypercard) and I used it everywhere I saw a nail sticking up. Perl's showing its age and I wonder what I think of python or php. Really all I need is a language that I'm still learning, so that boring little automation tasks are a fun challenge to discover and implement, rather than yet-another stupid perl or bash script.

Maybe by the time the bag arrives (four or five business days!) I'll have an idea of what language to learn. Or maybe I'll just flip a coin.

The Index Card Trick

Every day you have an index card (Mac OS Stickies note) with the five things you're gonna that day. My lists are things like "load OS on blahblah" or "do draft project plan for froofroo" -- real accomplishments, not just fiddly bits. But I'm really feeling like I'm getting a lot done, with just five each day. So I figured maybe my friends might want to try.

It's especially nice because five things is totally doable. Or you know exactly what got in the way. It's not a big critical path analysis on some monolithic project plan -- just five things. It's really working for me.

Oddly, some folks who have no idea that I do this, seem to understand what I mean when I say "okay, I'm putting that on my index card for tomorrow." Maybe it just sounds official.

Data Exhaust

I was thinking about data exhaust on the ride in, and I was still thinking about it at my afternoon tea break. So now I will share. I guess the idea of spending my time collecting, redirecting and analyzing the torrential flow of data that modern life creates -- well it sounds like a dream job! It's a cyberpunk thing, the "digital seer." Or maybe they'd have said "shaman."  Hrm.  A little to froofroo mystical, maybe.

Basically it's what a sysadmin does already for part of their day. It's the especially fun part -- look at all the metrics and figure out what the *actual problem* is. Folks tell us "this server is slow" and we run a couple commands and tell you that you're probably missing some indexes on your database, even though we didn't look at the inside of your database. It's like magic, but not at all.

Wouldn't it be interesting to try to formalize or mechanize that? Watch and see what handful of tools you use to take the pulse, then make that an automatic script? Isn't that basically what the data visualization nuts are doing -- translating metrics into something that doesn't require "work" to explore? Are there tell-tale metrics (or ratios of metrics, or red flags) that let you see the proteome of a running system, so to speak? If you show others how it's done, is it still magic?

Maybe that's exactly what I like about my imagined profession.

What if our diagnostic craft stopped looking like magic and started looking like art?

Arduino Mini

Got my Arduino Mini yesterday, and hooked it up. Here it is with both the main board and the USB adapter fitting on a mini breadboard, saying hello world (on pin 10, rather than 13). The reset button is wacky, 'cause it's got to bridge adjacent pins, so it's kinda diagonal there.