Welcome to WireWorld. It serves no other major purpose to waste the Wirehead's time, entertain, and let you know a little bit about the Wirehead.

Recent updates:

A bit about my recent baking obsession... or... ugh, baking cookbooks
A coincidence of things has enabled a bit more baking than usual. First, I'm riding a few more miles to work, so suddenly I'm able to eat a bit more carbohydrates. Second, I'm not working at a place with catered lunch. Which pretty much puts me back into the same sort of state of annoyance I was the last time I was doing a bunch of baking... all of the cookbook suck.
10G Ethernet is a Small Form-Factor Pain in the butt
I found out last week that my coworkers were all unaware of what’s been happening to Ethernet while they weren’t looking. See, Ethernet, all of the way up through Gigabit was mostly reasonable. First, they’d make some bad standards, like 10BASE5 or all of the weird not-quite-100BASE-TX standards or the time delay between 1000BASE-CX and 1000BASE-T where Gigabit Ethernet required shielded-twisted pair. Then they’d figure it out and we’d all get a reasonable standard for things that everybody was cool with, where the early-adopters generally were annoyed, but not overly so because they knew what they were getting into.
Some bike stories from this interviewing cycle
I saved all of these stories for after I'd finished switching jobs...
Savvy copyright messaging with responsive images
A long long time ago, I followed Derek Powazek's "Savvy Approach to Copyright Messaging" because, of all of the possible ways to reduce the chances of my images getting borrowed by other folks on the Internet, it seemed to be the best. I see DRM as a fairly dangerous technical equivalent of fighting windmills... It only works if you create a set of laws to enforce compliance which only serves to create new and more annoying problems for the world. And obtrusive watermarks are just lame and ruin the enjoyment of the image. By comparison, Derek's method adds a little nubbin on the bottom of the image, but then hides it. Which means that the second you view the image outside of the context of the hosting site, you see a reference to where it came from. However, as I'm moving all of the sites I host over to the new rm3 engine, I wanted to figure out how to make that trick work with responsive images, which I haven't seen anyone document how to do yet.