How DO you say “chorizo” in English anyway?

Overheard at a local Mexican restaurant:

emp1: This guy asked me how to say “chorizo” in English, but I couldn’t think of the right word.
emp2: That sucks. I can’t either.
emp1: (looking at me) Do you know how to say “chorizo” in English?
me: Nope. I just thought everyone knew what it was.
emp1: Right! It’s just chorizo. I don’t want to tell him what it is because he might not like it.
me: You could tell him it’s like a mashed up hot dog. They’re made from leftover ‘meat’ too.

It IS good with eggs though. Yum.

What kind of person keeps Trojans in their desk anyway?

I left my old job about a week ago, but the week before this the company had decided to move all the IT folks down a floor. We were in a four story building, and it had been laid out where the division executives were located on the fourth floor, while the data center and IT staff took up about half of the third floor, while the second floor remained party occupied.

I guess the folks at old job figured they were wasting money having so much space free so they decided to rent out the fourth floor and bump everyone down a floor. I tried to convince them that I was moving in a week and that I could save them money by not moving, but no go.

Now the director of the developers was out of town for the move, so his admin had to box up his stuff and move it for him in his absence. The only problem was that the ‘boxes’ were see through tupperware containers, so when his stuff was moved to the new cube the internals were all on display. Several coworkers noticed that along with pens and pencils he had a pack of Trojan condoms packed into his boxes. I’m not sure why a married man would need Trojans in his desk at the office, but maybe I haven’t thought about it from all the angles.

Whatever the case it sure is creepy to see that stuff at work, not to mention being the guy that keeps them there. I can handle toothbrushes (that just hygienic), even razors, but condoms? That’s just creepy. So take your condoms home before you move; no one wants to see that.

Judging from various sources, it’s like people WANT the stupid “Browser Wars” to happen. Again.

I’ve seen a few posts here and there about Flock over the past couple of days or so but I didn’t find it interesting enough to follow through and find out what it was, but once it appeared on Slashdot I figured it was worth a look.

In addition to many comedic reactions references to bird and lemming-like behavior all, the posts I read about Flock had this creepy “we want to see a fight!” ring to them. I guess people forgot that the end result of the last browser resulted in a four year stint of no browser innovation! I’m all about sidestepping bureaucracy when the red tape is too thick, but how hard would it have been to bite the bullet, stick to the Mozilla plan, and just design a suite of extensions? This guy set up a site just to play with posting from Flock and notes that it does have some cool features that the Firefox base doesn’t come with (which is totally true), but I’ve found extensions to do most of them. It’s not going to help OSS success all that much to have practically the same products competing with each other. That’s almost as silly as fighting over keeping a single button mouse.

On the upside, at least this won’t (I hope, god I hope) add yet another browser to the list when coming up with CSS.

I guess this explains why he started a new blog to try out the Flock log posting

Consolidating multiple shared server domains into one

For a few years now I’ve kept the domain this blog runs on separate from the domains that I use for my email delivery. I no longer see any reason to keep the content seperate so I decided to see what I needed to do in order to consolidate these two sites into one shared server site.

Now since Brandy and I actively get email to the domains on the moving site and I didn’t want to edit any posts to point to a new location, I had to set up a few goals (listed below) to accomplish in the move. Once these goals are all met the change shoudl be fairly minute, although I can’t really test to see if these work until going into production. Luckily my users are understanding and won’t cry too much about down time (har har).


  • Redirect links to point to the new location transparently
  • Ensure that email service is not interrupted
  • Consolidate static content from old sites into one directory to ease WordPress upgrades

Goal 1
Before I started using Flickr I used a couple of different locations to store locally linked images. Since I wanted to not break these existing links I decided to use an .htaccess file to provide the redirection to the new file locations. The general syntax for .htaccess files can be found here, and my entire .htaccess file can be accessed through this link.

Goal 2
Making sure that email didn’t get interrupted was a much easier task that the redirection, since Brandy and I are the only 2 users for these domains. The task is especially simple since these domains are just forwarded to GMail to take advantage of their above average spam filter. I simply had to recreate the users on the new domain and then just create the .forward file in each users directory with the email address to which to forward the mail.

Goal 3
This was the hardest goal to accomplish and I’m not a huge fan of the route I took to accomplish it. I had previously had a “download” folder where I put random files that I linked to or installed on the site, but in order to change the name of the directory I would have to change up an untold amount of posts. In order to avoid this situation I decided to just keep the name and move old and new static content underneath this existing directory. I really wish I could have changed the name, but I didn’t feel like searching around the logs that much for links to redirect. Oh well.

So I think I’ve found viable options for the domain consolidation, but I’ll find out for sure after the switch is made on the server side. If there are any serious changes I’ll post an addendum. Hopefully everything will go smoothly, but I can’t imagine there will be too many complaints even if there is an ‘outage’. It’s not like I’ve set up service or expectation levels with myself or anything.

Bloglines now has keyboard shrtcuts

I logged into Bloglines as usual and saw that they have taken the Google path and added keyboard shortcuts to their interface. I can’t find a direct link to the shortcuts, but they are described below.

I’m pretty excited about this, being a keyboard guy, but I really wish they had used the same layout as Google. Both services are pretty content-related so the controls of each interface are about the same, and it would have been nice to only have to remember one set.

Hopefully this new rash of AJAX applications doing bring in a new era of vi versus emacs layout fighting; as if tech guys didn’t already have enough standards to argue about already.

  • j – next article
  • k – previous article
  • s – next sub
  • f – next folder
  • A – read all
  • r – refresh left pane

Update (10/13/2005 15:15):
I found the link to the new Bloglines shortcut keys, via the Bloglines pseudo blog.