Back in High School (1990 and 1991, to be specific), I was a student pilot in the Adrian Soaring Club, flying out of Lenawee County Airport in southern Michigan. I trained with various instructors in their Schleicher ASK-13 wood and cloth glider.
According to my log book, I flew 23 times totalling roughly 6 hours and 41 minutes of time in the air. Yes, some of the flights were short--like the unplanned rope break exercise at 180 feet. It was challenging and fun. But I ran out of money before I could solo. I was close. Quite close if I recall.
By the time that ended, I was flying on my own. I'd fly takeoff, tow, landing, and everything in between. The instructors were along for the ride to make sure I didn't screw up and to help me practice more advanced maneuvers (I had a few left to learn).
Fast-forward 11 years. I recently discovered that a friend of mine at work had just started taking flying lessons--in gliders! I had always planned to get back into the cockpit someday so I jumped at the chance to start flying again.
We fly as part of the Hollister Gliding Club in Hollister, California. It's roughly a 1 hour drive south on highway 101 from where I live in the Santa Clara / Sunnyvale area.
I've started a separate flying blog to record my aviation adventures and related stuff. (There are three entries as of now: one, two, and three.) I may occasionally post any really interesting or important stuff in my main blog, but if you're curious about my progress, I suggest to read my flying blog.
Oh, there may be a couple bugs while I get the flying blog working. Lemme know if you see problems. I know, it needs template and CSS work yet.
It sounds like I'll be helping with some multi-terabyte MySQL tests in the not too distant future. This is good not just because I get to play with neat toys, but it'll finally help me to answer the "how well does MySQL deal with BIG data sets?" question. Until now, I've had to appeal to my knowledge of how MySQL works as well as some second or third-hand reports of what others have done in this area. It'll be nice to have some concrete data and tests that I understand and can explain to others in detail.
Stay tuned for more.
Had dinner last night with Jim and James, the creators of HotOrNot.com at The Tied House in Mountain View. Interesting discussions about Yahoo's former practice of assimilating other companies, weblogs, TiVo, and lots of other stuff. They're good guys. I hope to hang out with 'em again sometime.
It's unofficial and unsupported. Use at your own risk. It's version 0.99.21. It's here. It fixes some very annoying bugs that users of 0.99.19 are likely seeing.
If you'd rather wait for the next official one (rumored to be 0.99.22) hang on a week or two. It'll probably appear on im.yahoo.com.
Over at Web Voice there's some discussion of an issue that Y! Finance and Y! News deal with constantly--how much "related" information about a keyword, topic, story, person, etc. is too much? Does it belong in-line or off to the side? Should the user be able to customize it? How?
This is interesting to me because I was supposed to be working on a project for Y! Finanace that changes the way we handle those in-story links you see on biz.yahoo.com news articles and commentary. But since I'm moving to Y! Search, I won't have time to work on that project. Too bad.
Anyone have strong preferences on this? Seen a site that does it exceptionally well or poorly?
As noted here, Phil is resigning as Utah's CTO. Damn. I liked reading about the tech happenings in Utah.
Oh, well. Good luck with whatever you do next, Phil. Keep us informed. :-)
Made it back to CA last night around 7:30pm. The cats were glad to see me. Or maybe it was just the catnip toys I always bring back after a long break.
Tons of catch-up at work to do. Lots of crazy stuff. Oh, and they're trying to move my office soon too...
Wow, look at all the snow coming down. I got to drive thru it a bit today as I was coming back from lunch with Josh. Oh, well. I'm flying back to California tomorrow, so I won't be seeing much more of this, I hope.