The old saying is just one letter off -- it's not the meek, it's the geek. I'm sitting in Portland Airport in Oregon waiting for a redeye, and the wifi is up but the DHCP server is dead. PDX is an enlightened airport, offering free WiFi for the entire airport (when it works) and I have a few hours to kill before the soul-sucking cross-country flight, and I really needed to get some work done. So, where most of the world would have given up in frustration, I simply ran tcpdump on my WiFi interface, found traffic on the local net which told me what subnet was in use, and I picked an ip high in that range, guessed at the default route (it was .1), specified a public DNS server I run, and voila, I'm posting this entry.
Between that and the knowledge required to successfully configure Bluetooth contact list synchronization, us geeks have it all tied up.