Massive props to those who poked my site. Makes me feel neat. Also props to Joey for certifying me. Whoop. Can I be the official Advogato troll? :)

I overcame NFS today. Evils associated with TI's obfuscated network. This guy helping me was trying to mess with 'netgroups' or some Sun/HP-UX construct like that. Oye. Turns out he may be quite intelligent; he showed me the hardware emulation rigs they have (scary) and he had a lot to do with the Compaq dual ThunderLan (tlan) cards. He could be just making stuff up though. It's for certain that he can talk your ear off though.

I've been thinking on ways I could start writing more code, be more 'uber'. One thing my friend Hai does is to just write something to prove to himself he can do it, like a texture mapper. I might do this in the applications/system realm; I think it'd be fun. My other two ideas come from the Software Carpentry competition. I'd like to write a modular test suite, with some ideas I've had in the past. I'll detail that in a second. My other idea is to real software quality testing on big stuff. Like toruture testing. I imagine something like Apache already has this in place, but I'd like to run long tests with lots of possible mangled input and do fail testing, produce lots of statistics, etc. Perhaps that could feed into writing the test suite.

The idea for the test suite is that you have a core, which provides generic testing services like logging, scripting, statistics, etc. It knows nothing about the kinds of tests being performed. Above that you have two (maybe more) kinds of modules. 1) test modules which test a piece of hardware, a webserver, a GUI application, etc. 2) extensions which probe the hardware, webserver, etc. I know that's a really rough description, but input is appreciated

Going to an 80's Frat party tonight. Gonna yell "Freebird!" all night. Shun me.