Code, monkey, code

I’m back from a gprs-free week in sunny cyprus. I was surprised to find that I can read the Greek alphabet quite well, courtesy of years of physics. Great ideas included hiring pedal boats to get away from the crowds, scooters to explore the island and finally taking 15 minutes out to order food to be delivered a few hours after we got back. Still, back in Edinburgh again … there’s more need for overcast-cream than suncream here.

I installed the 2.6 linux kernel a while ago, including udev but never played with it. Now, after a bit of editing, I have it giving all my various USB devices sensible names and I’m knocking up a script to automatically refresh my MP3 player with a new set of tunes every time I plug it in.

I’ve also been a passive observed of del.icio.us for a while, but I’ve now created my own area there which means I can find bookmarks filed by people with similar interests. The idea has been around for a while. Delicious is just a pretty neat implementation.

I want to set up a calendar/todo/contacts which is accessible from home, work and mobile. Multisync looks useful, as is this review of calendar software. But my wishlist keeps growing …

I’ve been asking the guys at Perforce.com how to simulate aegis-like “staging areas”. The idea is that developers commit their changes to the “staging area”, a script runs to make sure it builds cleanly on win32/mac/linux and passes the smoke test, before pushing it to the main “known to build” tree. It’s not clear to me that syncing between branches works, since you want developers to be updating /from/ the known-to-build stream but committing to the staging area. Hmm.

Finally, I’m currently reading through a biochemistry textbook with a view to exploring backyard DNA computing. How hard can it be? 😉