It is Bee Week! This year there are 293 contestants competing for the top speller honor in Washington D.C.
I have been busy trying to figure out if there is a way for Amelia and I to see it on TV. Supposedly the finals are going to be televised on ABC Thursday evening, but I found the local listings confusing and I’m not sure if this is true. Also, because I’m a recovering addict, we don’t have a television, so that complicates things further. Anyway, as a great speller wanna-be (I am a high school basketball star with Michael Jordan dreams) I find it all very exciting. Participating in the Project Read fundraiser (spelling) Bee last fall and coaching Amelia this past winter has reignited my interest in spelling bees. Fortunately, I found that the internet can help with the desire to hear all about it.
1) You can test to see whether you would have qualified for the quarterfinals last year. (Pmom: Yes! Of course since I’ve had an extra 25 years to study, I’m not sure how impressive beating out all those 11 yr olds is). Scripps will post 2009′s written test words tomorrow, I think.
2) You can check out this throwing things blog (also known as alott5ma) . Last year they offered a super play-by-play of the bee and they have a fairly comprehensive list of twitterers and bloggers concerned with this year’s bee (but check the comments on that thread, because I added another one!).
3) You can also check out biographies of the spelling bee contestants at the official Scripps site and read CNBC Darren Rovell’s picks for the kids to watch at the Bee. — Go Kavya, go!
Comments
2 Responses to “National Spelling Bee 2009”
Leave a Reply







As requested, I took the spelling test… but it won’t give me a score. I spelled all 25, checked them, and it went to a page that says “word 26 of 25,” but doesn’t have a word there… and the “next word” button doesn’t do anything.
Frustration!
Oh, sorry to have led you into frustration. The Scripps spellings tests while very cool, seem also to be quite buggy. I should have warned you. I had exactly the same experience as you on my laptop. When I tried it again on the desktop, it worked fine. I have no idea what makes the difference. Perhaps it’s a browser issue?