Review: spicy food

I saw that Wendy’s had introduced a new spicy chicken sandwich, and I like spicy stuff, so I had to try it. It had pepper Jack cheese, spicy chipotle sauce, and jalapenos. So how did it measure up?

It wasn’t as spicy as I was hoping for. If you want a mass-market spicy sandwich, I’d opt for the spicy chicken sandwich from Jack In The Box.

Until recently, Silicon Valley had another option: the habanero hamburger. The Prince of Wales Pub recently closed, but for a long time, it was the spiciest burger in the valley. A few years ago, a Googler stumbled across this bit of valley history:

Eating a Habanero Hamburger was once a rite of passage for new and departing operating systems engineers at Silicon Graphics. The tradition is apparently still alive and well in the graphics group. Having set the Silicon Graphics company record for number of Habanero Hamburgers consumed, Brian Totty brought the fine tradition to Inktomi Corporation.

That sounded like a neat idea, so a few years ago several of us Googlers made a pilgrimage to the pub in San Mateo. To make a long story short, the habanero burger was painfully hot. The habanero part referred to a thick red paste that sat atop the burger patty. After we ate the burgers, the staff clued us in on a few tricks: ordering the burger with mayonnaise or a glass of milk would reduce the burn. Knowing that beforehand would have saved a day or two of intestinal discomfort. 🙂 My wife couldn’t believe I was willing to eat an entire burger — but it was a good bonding experience with some fellow Googlers.

The pub is closed now, but there’s a video of someone eating a burger. If you watch it, you can see the burger heat from their facial expressions. The Prince of Wales Pub evidently closed in January 2007; does anyone know where else to get spicy food in Silicon Valley now?

Bacon polenta

(another post-without-particular-polishing)

You have to leave room in your life for serendipity sometimes. For example, without an accident, I never would have discovered the joy of bacon polenta. (All the people who say “Matt, I thought you were going low-carb?” can step off. I’m playing hockey today. I’ll skate it off.) The Google cafe may like to call it creamy polenta, but as a Southern boy, I just think of it as cheese grits. It’s even better with bacon. Mmmm. Bacon-y goodness.

Accidents in crawling/indexing/scoring happen too. Sometimes they’re happy: “If we turn this factor off, scoring gets better? Cool!”. Sometimes they’re unhappy: “What happened to this page?” One of my least favorite accidents is when someone reports a 301 or 302 problem. The heuristics we put into a place have greatly reduced complaints about “302 hijacking.” For the first time in ~1 month, I got an email about a “302 hijacking”. This case was especially interesting because I got an email from both sides: someone from the destination site wrote, and the source site also wrote to say “we didn’t mean for this to happen.” I take that as a kinda good sign; when I hear about it from both ends, 302 problems are hopefully much more rare. I passed the info on to the mailing list we have for that, and I’ve asked a colleague to email both sides when we get it debugged.

What do you do if you suspect a “302 hijacking” but don’t have my email address? There’s a convenient way that should get your report to the same engineering list, where it will get the same level of investigation. Go to and click “I’m a webmaster inquiring about my website” then select “Why my site disappeared from the search results or dropped in ranking” and click continue. In the webform that you get to, make sure you put “canonicalpage” in the Subject line, then put the details in the Message body. Someone will route that message to an engineering mailing list where we dissect claims of canonicalization problems (that is, picking the wrong url).

I also got one email today about a site being indexed under both and The proper procedure (assuming that you want to show up) is to make do a permanent (301) redirect to The person that wrote said that we hadn’t crawled recently to find the 301/permanent redirect. I’d be curious to hear feedback (in the same way as the paragraph above) to see how many other people are running into this issue.