THE "UNBEATABLE?" PTERODACTYL

23:47

We want hen fap:

I went to this "College Club" place (in the middle of the workday) to attend a scheduled "chat" with 2nd tier celebrity "The Gus". Being in a chat room with lots of people in it seems a lot like what a switchboard operator might experience: "Hi" "Hi" "Bye" "Hi" "Bye" "Hi", forever. Douglas Coupland made a very good example in "Microserfs", back in 1995. It's still exactly as he described. You get this breezy feeling, like you're meeting a lot of people, but really, you might as well meet a phone book. Gus never showed as such, but someone named "Tussin2" showed up, speaking with slightly more motivation than a typical chat denizen. When Mr. T brought up the possibility that someone else in the room may actually be "The Gus", my suspicions were only increased. He didn't stick around though. If I were him, I would be (slightly)humiliated and disappointed by the pathetic turnout (2, maybe 3 folks, who wandered in and out). See, all the REAL action was going on in the "Lounge", where they were talking about how "guys think about sex all the time". Gahh.

At work, we've hired another programmer. I've got high hopes for this one, he's quick to catch on and quiet until he does. He printed out all of the source for the project I just completed, in order to get up to speed on it. While reading it, he came across some strange andr00-isms. I forgot about the possibility that people that don't know me may wind up browsing my source code, so when they do, they'll be skimming along happily and then run into something like:

SComp.SetOutputMode(HTML_MODE); // You're probably whale-loving yourself.

Which generates an immediate trip to my desk to inquire what it means. What it means is that source code gets pretty boring sometimes, and the occasional irrelevant blurb can make your concentration wake back up. Perhaps subtle wackiness pervades all industries involving typing. Who knows what lurks in the minds of bored technical writers? (Well, I guess technical writers do.) For instance, the back of a box of "Cheese Dippers" includes this instruction:

WATCH PRODUCT CAREFULLY - If cheese becomes visible, remove from heat immediately; the sticks are done.

"The sticks are done," indeed. I thought I was removing them from the heat because they were sweaty. The writer of those directions had restraint, at least. Sometimes I get out of hand, and the code itself becomes very silly looking.

honker.Select(sel_format,3,whereg,FUCK_NO);