I was reading
this article and it was close to home for two reasons: 1) I went to Florida State and it talked about Willie Williams infamous recruiting visit, and 2) it talked about he was the only passenger on a commercial flight. The second point sounds like a stretch, but it can happen.
Years ago, I was flying from Phoenix to Denver. I got to the airport early and went to the United Red Carpet club as my flight was delayed. My flight was so delayed that the "next" flight was scheduled to leave before mine. Because I was in the Red Carpet club, I missed the announcement they were putting everyone on my flight on the next scheduled flight, which would actually leave before my originally scheduled flight. Since I missed the "next" flight, they put me back on my original flight, which actually left after the "next" flight. Got all that?
I got to the gate and looked curiously around as I saw one other gentleman sitting in the waiting area. The plane was there and they weren't boarding yet, but the flight was leaving in 35 minutes. The started boarding, and the gate agent announced that we could board. The entire passenger manifest was me and one other guy. Needless to say, we got upgraded to first class.
The flight attendant pretty much blew off the pre-flight instructions - she came up to us and said "You both look like you've done this before and you're buckled up - do I need to go over everything?" We said no, and she brought us drinks. She told us she'd be in the first row of coach if we needed anything. I'm sure someone at the FAA is probably having a coronary right now, but I know what to do if the fit hits the shan.
The pilots had some fun with it, too. A few minutes after we leveled off, the pilot came over the PA and said "Good afternoon, gentlemen - both of you! Sean, if you look outside your side of the plane, you'll see the Grand Canyon. Jeff, on your side you'll see [whatever it was to see]." We had a good laugh and the service was great the whole flight.
It was a surreal, interesting experience to be one of two passengers on a 737.
I'm currently working on an application originally written in classic ASP for a customer. Several thoughts come to mind:
- WhoTF would start building an app in 2007 in classic ASP instead of ASP.NET?
- Classic ASP sucks. Everything is a kluge...I've had to manually write all sorts of AJAX crap, things that should take 10 minutes take 2 hours, my business logic is intertwined with the interface (I'm using classic ASP classes, but what a fake substitute for a real OO language) and performance is slow.
- The previous developers on this thing deserve a special place in the unemployed developers line. They need to go back to school. And yes, I realize everyone else's code always sucks and I didn't write this crap. But this is really bad. They let this into production:
Sub AllowAccess
Exit Sub
End Sub
I could go on and on with the bad code examples, but I don't want to make your eyes bleed, too.
Man, this project is annoying!
There's a bug in the instructions for removing a table using SQL Compact Edition that drove me nuts for about 20 minutes. I tried the intuitive way which is what is documented in the help, but which is also wrong. The instructions read:
1) On the View menu, click Server Explorer.
2) In Server Explorer, expand the data connection from which you want to drop a table.
3) Under Tables, right-click the table you want to delete, and then click Drop Table.
4) In the Delete Objects dialog box, click Remove, and then click OK.
Step 4 should simply read "Click OK". That will drop the table. If you click "Remove", it removes the table from the list of objects to be dropped, so when you do click "OK", it doesn't actually get dropped.
I must've tried as instructed in the help (without actually reading the help first; it was just intuitive) before I thought maybe I shouldn't click Remove first. That did the trick.