Ah, geekhood. There is no better way to spend a lunch break than with cheddar scrambled eggs, apple-plum smoothies, Ben Folds playing, and chuckling ironically over recognizing big balls of mud in your life. (To anybody who ever sees my old robotics code again: I'm very, very sorry. I actually put in docstrings now, I swear.)*
*Although that code was better than the infamous schoolbus algorithm simulator I wrote in high school for a math modeling competition. I had not yet learned about objects. It was 17 double-sided tiny-font printout pages of one giant while loop that tunneled through multiply-nested arrays declared in Hungarian notation. After we placed in the competition, I deleted the files in disgust and decided to learn about OOP. (The sad thing was that I was the team's sole coder because they needed one for the girl's group - there were no mixed-gender teams - and there was literally nobody else.)
Found a veritable bonanza of reading materials about Information and Communication technologies for development (as in "the developing world," though I... have my reservations about that term).
Also, you can use vim as a wiki. (Translation: Do you also like keeping your notes in plaintext files? Now you can link them together without making them non-plaintext files.)
Just ran across my notes from when Henry taught me about the trinity rescue kit, which you can use to recover severely borked systems. Of course, I had to ask how one would prevent malicious use of the TRK to grab data from a hard drive without authorization, so then he showed me truecrypt. The tradeoff: if your encrypted data's borked, it's borked. It's kind of scary how much of "security" is just a thin shiny layer that makes us feel good. (Also helping with this mental shift: my further adventures in learning lock-picking.)
I'm drowning in emails. I think I will section off some time to attack that after a meeting this afternoon.