The Latest

  • Interior bike rack for a 2012 Ford Focus hatchback

    The best way to carry a bike?

    I want to be able to carry a bike in my car. Both so I can have my bike with me on road trips and to try new trails outside my normal riding distance from home.

    The obvious way to mount a bike on a car is to put it on a rack the roof. Turns out[1] it’s also not a great solution for reasons I’ll get into. Other common options are hitch carriers and trunk lid mounts. I can’t abide trunk lid mounts, and I don’t plan to install a trailer hitch on my car. And though I’ve had a roof rack in the past, I don’t have anything that will fit my Ford. I’d need to buy new towers, cross rails, and bike mounts. That’s expensive.

    Roof racks have other disadvantages. Bikes on the roof reduce gas mileage on road trips and expose the bike to potential damage. You have to be careful about parking garages, and you have to get locking fork mounts if you plan to leave your bike with the car while doing other things. In contrast, mounting the bike inside the car preserves gas mileage, protects the bike, keeps the exterior appearance of the car stock, and lets you keep a bike with you while doing other things with less worry about theft[2].

    For these reasons I’d prefer to mount the bike inside the car. In fact, part of my selection process for purchasing a car included a requirement that I be able to easily place a bicycle inside the car. Ideally with minimal to no disassembly required. This was part of the reason I eliminated all sedans from my list and focused on hatchbacks and wagons.

    Rack ideas

    Although I wasn’t as comprehensive in testing this as my friend Andy[3], I was certain that the Ford Focus would accept a bike and meet my criteria. I just didn’t work out a good solution until after spending some real quality time with the car. Things started to click after my recent Iowa vacation, when I got a good look at the custom racks Andy built for his Edge, his wife’s XTerra, and my dad’s Nissan Frontier.

    Andy can carry two bikes upright in a set of Rocky Mounts mounted on stubby Thule cross rails. He folds half the rear seat of his Ford down and the carrier assembly is held in place by bungee cords. Simple, relatively inexpensive, and allows him to easily carry three people and two bikes. His wife’s XTerra is similar, but can carry three bikes with the back seat folded flat. It uses a set of truck bed mount style fork blocks in a custom rack. Between them then that’s five bikes and five people in two vehicles. Nice.

    My dad’s rack is a simple folding wooden frame, custom sized for the bed of the pickup, with two simple fork mounts bolted to the frame. That and the ribbed pickup bed are all it takes to securely hold a bike in place. It is designed to carry two bikes, and can take three in a pinch, with the front wheels either in the bed of the truck or behind the seats in the cab.

    I wanted to do something similar for my Focus, despite its smaller size, and these existing mounts were a good starting place for my design.

    Test fitting

    I started testing bike fit when I got home. A few test arrangements (and unfortunate grease marks on the ceiling of my car) later I had a workable solution that required removing only the saddle and the front wheel of the bike. I did some test loading and unloading and I can get the bike unloaded, assembled, and ready to ride in a couple of minutes. I can prep the bike and get it loaded back in the car quickly as well.

    The key to loading the bike turned out to be to fold the passenger side of the rear seat flat (the narrower half of the split seat), and to temporarily fold seat back of the driver side as well. The bike can then be rolled at an angle into the cargo area rear wheel first. The angle (tilted down about 45 degrees) allows the rear of the frame to clear the hatch opening, and once clear the bike can be tilted back to vertical and the larger side of the rear seat placed back upright.

    After working out the test fit, the next step was to build something to properly anchor everything and keep the bike from damaging the interior of the car. The primary anchor had to be the front fork, with the rear wheel anchored by it’s location in the gap between the folded rear seat and the door. Realistically the only thing I needed to build was a front fork mount.

    Designing the fork mount

    The tricky part of designing the mount was that I didn’t have a lot of clearance between the rear window of the hatch and the bike’s handlebars. A simple fork block mounted to a set of 1x4s would raise the handlebars too far off the floor. After some thinking, I sketched out an idea for mounting a fork block horizontally to the side of a piece of angle aluminum. This would minimize the rise of the fork mount above the floor of the trunk.

    I picked up a fork block at the bike shop, then headed to the hardware store for the rest of the parts. The primary assembly is simply the fork block mounted to the side of angle aluminum. I finished it off with nonslip shelf liner to protect the interior of the car from the sharp metal edges and to keep it from sliding around on the floor of the car.

    Parts list:

    • Basic fork block from the local bike shop. These are widely available and are really just a metal bracket with a quick release skewer and mounting holes.
    • Angle aluminum, 1.5 inches by 3 feet, 1/8″ thickness. The main body of the mount. The width of my trunk where the bike fork sits is 37 inches from wheel arch to subwoofer. The 3 foot section of aluminum is just about perfect. The 1/16″ thickness was too easy to twist, but the 1/8″ was nearly ideal.
    • Bolts. I bought a small bag of short 1/4″ bolts and nuts that fit the holes in the fork block and wouldn’t extend much past the angle aluminum and fork block.
    • Nonslip shelf liner. I got a roll of standard black nonslip shelf liner to both pad the aluminum, making it safer for the car, and to keep it from sliding around on the floor of the trunk.
    • Heavy duty mounting tape. I used a roll of outdoor mounting tape to secure the shelf liner to the aluminum bar. I think most any adhesive would do.
    • Miniature bungee cords. These are to secure the front wheel to the bike frame and to mount the seat between the fork blades. I am thinking about switching to velcro straps.
    • Drill and bits. Technically tools rather than parts, but necessary to drill the mounting holes in the angle aluminum.

    Not including the drill (which I bought a couple of years ago for my garage wall mount bike rack project), the total cost of parts was about $60.

    Construction

    Construction was straightforward. I first started by loading my bike into the car without the fork mount, and tried to find the optimal position of the frame and fork for clearance of all bike parts from the interior and easy closing of the liftgate. I placed the angle aluminum under the fork, and centered it between the wheel arch and the subwoofer. I then placed the fork block into the fork and verified that the position would work, and marked the location of the mounting holes.

    Drilling the holes was largely straightforward, but I had to do it twice. I had marked the holes with permanent marker but had not been careful about cleanly covering the outline of the fork block. Because of this my holes were about 1/8″ too far apart, and the fork block had no horizontal forgiveness in the design. I moved the block slightly and re-drilled the holes more carefully, and the second time things mounted fine. I didn’t really mind, since I don’t get enough opportunity to use my nice cordless drill and this was a good excuse. I finished the edges of the drill holes with a small grinding bit on my dremel.

    The fork block was bolted to the inside of the angle aluminum (though the outside would have worked as well), and in this configuration the mount point for the fork blades is only about 1/2″ above the floor.

    Once I verified the fit of the assembly, I pulled it back out of the car and wrapped the outside of the aluminum in the nonslip shelf liner. This probably took the most time of the whole process, but most of that time was fiddling with the tape I bought. I probably should have used a different type of tape, but it’s done now.

    The finished product

    The finished fork mount is extremely simple. It’s essentially just an off-the-shelf fork block bolted to a short section of angle aluminum. It solved the problem though. The front of the bike is held securely in place to the aluminum, and the mount’s length and the nonslip finish keeps the bike from tipping or sliding around. The rear wheel is held in place by the friction of the tire and its position between the door and the rear seat cushion. Even spirited driving around town didn’t shift the bike around. I lose some luggage space, of course, but not a lot, and this will let me easily bring my road bike with me on road trips without hurting my gas mileage or damaging the bike.

    What about two bikes?

    Because the car is not long the bike has to sit at an angle as the photos show, with the rear wheel at the outside of the car and the fork blades toward the middle. My handlebars are also relatively wide. In the current configuration it would be difficult to load two bikes side by side.

    I think it would be possible to load two bikes at a time by building a second set of mounts (or even placing two fork blocks onto one mount), but this might require removing or otherwise turning the handlebars of both bikes. Another option may be to mount the second bike “backwards”. I might test these possibilities at another time, but my primary goal was to be able to easily bring my road bike with me on trips, and I have accomplished that goal.

    Why I wrote this

    More than anything, I hope this (admittedly crude and simple) mount option will be useful to owners of the 2012 Ford Focus hatchback and other similar-sized hatchbacks such as the Mazda 3 and Subaru Impreza. The basic concepts might even be useful to those with larger vehicles. It strikes a good balance between preserving seating and cargo space while minimizing the bike disassembly required to use the rack. Loading a bike can be accomplished in 5 – 10 minutes, start to finish. It is very light, has only one moving part, can be hung on a nail on the wall of the garage for storage, and it was easy to build.

    — Steve


    1. You have to say it in your head like Merlin would on Back to Work to really get it.↩︎
    2. There’s never no worry about theft.↩︎
    3. Andy actually made cardboard bike mockups that he took to dealers during his shopping process to check fit and make sure whatever he bought could take two bikes minimum.↩︎

  • Brewing an English bitter on a hot day

    It’s hot. I brewed.

    We’ve been way above normal all spring and summer so far, and here we are on what is expected to be the second 100 degree day in a row. And I made a yeast starter last night so despite the heat I spent the morning outside on another brew session.

    Today’s beer is another kit from Northern Brewer called The Innkeeper. It is a straightforward beer with added corn sugar to up the gravity. This is my second all-grain brew, and though the first went very smoothly I’m still not confident yet. The only way to get there of course is to just keep brewing.

    The process

    I started the brew proccess at around 10 in the morning by procuring a second propane tank. I’m tired of fuel anxiety and also don’t want to waste fuel by exchanging a tank early. Going forward I will keep a full backup in the garage for when I do run out. My burner appears to be fairly efficient and I didn’t run out of gas, but now I don’t have to worry as much.

    The process went a lot smoother than my first all-grain batch. I modified the valve on my mash tun so that the ball valve arm no longer interfered with the cooler wall. I also preheated the tun and took the actual temperatures from my first batch into account when calculating my strike water temperature. This time I nailed my target mash temperature, though with the huge air space above my grain bed (the cooler I use would be better for 10 gallon batches) I lost some heat and added another quart of boiling water about halfway through the process.

    Still, it went smoothly. And for once I had enough wort pre-boil that I ended the boil right on my target of 5 gallons. This is largely a result of learning over time how much volume I needed before starting the boil.

    Sparging also went smoothly, except that because of the size of my mash tun and relatively small amount of grain I had trouble establishing a good filter bed. I’m thinking maybe I should get a smaller cooler, but for now I just hope the addition of Irish moss 15 minutes from the end of the boil helped clear things up, along with the siphoning of the wort into the fermenter rather than pouring.

    Sparging also took longer than I would have hoped, at nearly an hour. I ran two batch sparges of 10-12 quarts each, which is probably more water than I should have ran. Measured extraction gravity was 1.030, which is close to target. Boil gravity was higher because of the additional corn sugar.

    The boil went smoothly, and measured original gravity, before aeration and yeast, was 1.044, just a hair higher than the target of 1.043. The beer’s in the fermenter now, wrapped in a cool wet towel to try to keep the temperature in the target range.

    Waiting

    Brewing is a lot of waiting, especially with an all-grain batch. There’s the 30 — 40 minutes to get the water to the right temperature, and then there’s the hour to mash, then another 30 — 60 minutes to complete the sparge process, then another 15 — 30 minutes to get the wort back to a boil, then an hour to boil, then 20 — 30 minutes to cool the wort, then another 30 minutes or so to get it transferred to the fermenter and aerated, and pitch the yeast. Then cleanup.

    Maybe others are more efficient, but my basic assumption was that with an approximately 11 am start I would be done in the middle of the afternoon. In the end, the brew finished with pitching the yeast into the fermenter at about 3:15 pm, and I finished cleanup at 4.

    I need to start brewing with friends so we can brew larger batches and tag team the process so that it is less solitary. Honestly as much as I enjoy brewing the step-by-step process is kind of boring and always frustrating.

    Results

    The results are 5 gallons of The Innkeeper now fermenting in the corner of the dining room. For the next few days I’ll keep a careful eye on the fermenter temperature. It’s simple enough of a beer that in about 3 weeks I’ll bottle it, and a couple of weeks after that I’ll be drinking an English bitter that has a reputation for being excellent.

    — Steve

  • Microsoft’s Strange Tablet Launch

    I don’t normally write this sort of thing, as I prefer to keep this site focused on my everyday life, but I watched the Microsoft Surface keynote video this morning and have been thinking about what I did and didn’t see. And although I am a long-time Mac user, iPhone user, and iPad owner, I was and am very interested in this type of technology and what Microsoft is able to do with it.

    So I’m sorry about this, and I promise I will get back to beer and road trips soon.

    Let’s start with the basics. Names. They’re calling the tablet “Surface“, which would be great except they already had a product called Surface, and other than touch this really isn’t the same thing at all (notably, they changed the name to PixelSense, another questionable name, before launching the tablet).

    Even stranger though, they chose to call the screen “ClearType HD”. ClearType has been around a long time, but it is not a hardware product. It was (is?) Microsoft’s subpixel antialiasing text rendering engine which is now over 10 years old. It doesn’t really make sense for them to try to shoehorn this name onto to display for their new tablet, but they did.

    And of course there is the discussion of whether it is really fair to call the Windows RT system “Windows” when it has none.

    But what I didn’t see was far, far more interesting.

    While Microsoft spent a lot of time talking about the design of the hardware, they failed to clarify some of the key details. Claims for pricing and availability were so vague as to be nearly useless. Screen resolution was implied but not stated. They never even mentioned battery life. How long do these things last? That’s important.

    Over and over the presenters discussed how “like a book” the Surface is when the keyboard cover is attached, but they never showed it held like a book, or being read like a book.

    Over and over the presenters discussed how with the keyboard attachment the Surface could be used for Real Work, unlike some other Tablets That Will Not Be Named. Ignoring the silliness of that claim, why were there no demonstrations showing Real Work on the Surface? Not once did any presenter show any Real Work on the ARM tablet, and all we got on the Intel machine (which is more like a traditional PC) was a very brief demo that Lightroom will run.

    The show spent so much time talking about the keyboard covers and yet we never once saw anyone typing with them.

    They didn’t even show what may have been the most obvious demonstration for this: reading and responding to email. This would have showed off the Windows RT system’s Metro mail client (being used for Real Work, of course) and would have supporting the claim that the keyboard cover really is easy to type on.

    And there’s more!

    We never saw web browsing (other than an embarrassing system crash). We never saw email. We never saw a calendar. We never saw book reading. We never saw a video or media player other than Netflix. We never saw a news reader. We never saw note taking. We never saw Office, or any Office-like program. We never saw even the most basic blank window with text being typed into it. We never saw an onscreen keyboard. We never saw a photo viewer or a photo editor. We never saw games. We never saw maps of any kind. We never saw the device in portrait orientation. We were told about the cameras but not shown video chat or Skype, which they own.

    The things we never saw far outnumber the things we did.

    We were told many things about Surface, but we were never shown any of them beyond the hardware itself and a few nearly static screens. It’s not enough to just be told. For this to have weight we must be shown. When Steve Jobs introduced the iPhone and later the iPad, he spent real time playing with them. He used the keynotes to show what we could do with these amazing new devices, not just how nice they looked.

    The kind conclusion is that Surface is unfinished. I think it is so far from being ready, software-wise, that they chose to avoid showing us the software as much as they could. And that’s really unfortunate because a good tablet is, fundamentally, nothing more than a window into the software it runs.

    — Steve

  • Completing Beer Prep for Andy’s Housewarming

    Tonight I bottled the third of the three brews that I’m bringing to Iowa for our get together at Andy and Lindsey’s new place in Des Moines. The beer was the simple American Rye Ale from the Northern Brewer Kit, the product of the smoothest brew process I’ve had so far. It should be ready to drink around June 29, the day I plan to be driving from Denver to Des Moines.

    Now I have a fairly good all-grain pale ale, a tasty Belgian ale, and a simple rye ale, and I’m taking at least 2 cases back to Iowa with me.

    I can’t wait to share this beer I brewed with my friends.

    — Steve

  • Buying the Focus

    I finally bought a new car, over a year after I first started seriously considering it. Say hello to my candy red 2012 Ford Focus.

    I’ve been a fan of small European hatchbacks for years, and lamented that so many of them never make it to American shores. We had the Golf, and the first Focus, but never had the huge variety of small, practical cars that the Europeans have. We also, for some reason, were denied the well made and well regarded Fords that they had in Europe.

    But then Ford finally brought their small, well made hatchbacks here. I was excited about the 2012 Focus spaceship from the first announcement I saw on Autoblog, and almost immediately started considering its potential as my next car. The Subaru Outback was getting old, and the Focus was great looking with a nice interior and great gas milage.

    This kickstarted my thinking about cars, and not much longer after I started looking more seriously we got the revised Mazda 3 and a new Subaru Impreza. I had already decided to focus my attention on small practical hatchbacks, and with so many changes in this category I stepped back and took a look at the overall market.

    There were certainly other cars to consider, but I decided to limit my market range. I excluded the smallest cars such as the Fiesta, Mazda 2, Honda Fit, Nissan Versa, and Toyota Yaris. I also excluded anything that couldn’t get 35 mpg on the highway.

    This pretty much narrowed down my choices to three:

    1. 2012 Ford Focus Hatchback
    2. 2012 Mazda 3 Hatchback
    3. 2012 Subaru Impreza Hatchback

    Yes there was also the revised Hyundai Elantra but I didn’t feel anything for it, and crossed it off the list early. I had driven several Fords as rental cars, including the most basic hatchback they sell and a nicer SEL with leather and a lot of options. Ben let me drive his Mazda for most of a day, and I did a more normal test of the Subaru.

    The Subaru was definitely the biggest inside, with the best sight lines and smallest blind spots. The AWD was a very tempting practical feature as well. It was also the least fun to drive and the least nicely put together inside. The Mazda was great fun to drive and might, by a hair, have the best drivetrain of the three. The Ford though was the best car overall, and it didn’t take much time to make up my mind. I’ve driven the previous Focus, and the difference in interior quality, fit, and finish are enormous.

    In fact, I essentially bought the exact car that Ford had brought to the Denver auto show I attended last year: same color and most of the same options. I remember the first time I sat in it and how much I liked it, and now I own it. It’s great fun to drive, with a firm suspension and smooth responsive engine, and all the “silly” toys I got with the option packages have turned out to be great. I love not having to take my keys out at all. I can walk up to the car and grab the handle and the doors unlock, then I sit down and hit a button and the car fires up. It’s like the future.

    Surprisingly, the built in navigation is actually good. Voice input works very well, including putting in a street address by simply saying the address out loud. POI searches can also be done by voice. In fact the whole voice control system in the car is better than expected. It is certainly not perfect, but responds to the vast majority of commands exactly as expected. I can choose music, control navigation, set the climate control, and make phone calls without ever looking away from the road. The rearview camera is very useful, and the automatic parallel parking worked exactly right the one and only time so far I tried it.

    And somehow, unusually, the Sony stereo and Microsoft software that runs it are actually tastefully designed. That’s just weird. And it sounds great.

    I’m enjoying the car more than I expected, and I have far fewer complaints than I expected. Even the manual mode is better than I was lead to believe. Reviewers had complained that a small rocker switch on the side of the gearshift wasn’t a great way to run the gear changes, and wished for paddle shifters or another system. Paddle shifters could be nice, but there are so many things on the wheel already that another set could just confuse things, and although I consistently pushed the gearshift lever on Ben’s Mazda the wrong direction when shifting, I’ve never made that mistake on the Ford.

    — Steve

  • A Warm and Windy Saturday

    Today was one of the warmest days of spring so far. I woke up early, with an orange sun shining in my eyes, but I wasn’t really awake. Eventually though I started to function, and made a good beginning on the holiday weekend.

    The morning included two significant brewing activities. First, I made a yeast starter so that tomorrow I can start the rye ale I’ve been waiting to brew. After that, I bottled the Belgian ale I brewed back in March. All told, this took a few hours, and I watched Total Recall and then The Sixth Day after it. A morning of Arnold sci-fi made sense to me. There were no real snags in either process, and now I have two cases of an about 8.5% abv beer bottled and starting to carbonate. They should be ready about the time we have our housewarming shindig at Andy’s place.

    Belgian ale

    Because I was up so early, and because I was kind of in a lazy state, I ended up taking a nap in the mid afternoon. Somehow that didn’t sit right with me though, and when I woke up I was feeling antsy. I didn’t want to feel like the day was wasted, no matter how productive. A nap and then staying home the rest of the afternoon would make it feel that way.

    So even though it was warm, and even though there was a high wind advisory, I pumped up the tires of my trusty and wonderfully rebuilt Trek bicycle and went for a ride. I had a goal of about 20 miles and I made it to around 22 despite the high winds and running out of water a mile from home. It was actually a really good ride, and just what I needed.

    Now I’m sitting in the patio having a homebrew and typing up this summary of my day. Soon I’ll make burgers and have another beer. A successful start to a long weekend!

    — Steve

  • Going Loud

    I got a new keyboard.

    It’s one of those fancy Das Keyboards that all the kids are talking about these days. To be more specific, it’s the recently released Mac version which has the keys labeled correctly.

    Instead of getting a new keyboard I had given serious thought to finding a high quality PS/2 to USB adapter and using my old IBM Model M (part number 1391401, manufactured on June 21, 1988) instead, but on this Mac I use the option key quite a bit, and the command key is of course indispensable. The Model M only has two keys on the left side.

    I could get around this, of course. One option would be to map the caps lock key to control, the control key to option, and the alt key to command, but that would be very strange for the muscle memory. Nothing is perfect.

    So instead I got a more modern USB keyboard with the correct buttons but a different type of mechanical switch. They do still make the buckling spring type of switch that the Model M uses, but most other mechanical keyboards either use Cherry or Alps mechanical switches. As far as I have been able to tell, both are highly regarded.

    I also wanted to stick to companies that made keyboard versions intended for Macs. It isn’t difficult to remap a Windows keyboard to work correctly on a mac, but it is preferable for the keys to be labeled correctly with no manual remapping required.

    Unicomp is the company with the buckling spring technology and they make a lot of industrial and POS type keyboards. They do have some Mac models but they are just about the ugliest things I have ever seen. I know that the Model M is frightfully ugly too, but it is allowed to be because it is 24 years old. You can get away with a lot just by being around forever and never breaking down. But there is no reason for the key switch technology to dictate the styling of the rest of the keyboard, and it certainly doesn’t require that the key caps and case they are mounted in look 24 years old on the manufacturing date.

    Matias, another manufacturer, has mechanical switch keyboards as well, which use Alps key switches. Unfortunately they suffer from a similar malady. The Tactile Pro 3 looks like a bad combination of the shape of an old Apple keyboard from the bondi blue iMac days combined with the styling of the mushy white crumbcatcher keyboard. They have a metal version too but the shape of the case is unchanged. I think maybe the problem is that instead of using a basic keyboard shape or developing one of their own they tried many years ago to be stylish by copying Apple and now changing tooling for a new shape is too expensive to bother.

    So it ended up coming down to the Das Keyboard as the only mechanical switch keyboard I could find that tried to stay out of the way; that tried to look elegant but simple, and used its own shape instead of copying something else. The Das Keyboard uses Cherry switches.

    The keyboard case is a very glossy black, and fairly simple in overall layout. It is a perfect rectangle, except for the logo area at the top right which widens out almost like the transition from the fretboard to the headstock of a guitar. The keyboard is not much larger than it has to be, which is welcome. The overall shape is actually similar to some of the keyboards Cherry makes for POS and similar applications, but is both simpler and more refined.

    It has the necessary Apple specific keys above the function keys, but they require pressing the fn button to use them. I haven’t yet decided whether to shift this so fn isn’t needed. The only questionable design decision is probably the key cap labels. They feel printed on and I worry that they will wear blank over time. The font choice and decision to use lowercase letters is also questionable.

    But these are nitpicks, and it looks and feels like a very solid, well-built machine. Hopefully I’ll be happy with the typing feel over time, and hopefully it will be as durable as my 24 year old IBM was.

    I had honestly forgotten just how loud a mechanical keyboard could be. I haven’t used my Model M as a primary typing keyboard in many years (though I’d hate to let it go), and I gave away another mechanical keyboard about 10 years ago.

    This thing is amazingly loud. Most of the normal typing motions are just sort of clicky, with a nice snickity noise as the mechanism trips and then a clack as the key reaches the bottom of its travel. It’s not quite the same feeling as the Model M gives, but similar. The larger keys, though, are killers. Enter and backspace are especially frightening. I think it has a lot to do with the overall size of the key and the somewhat alarming force with which I slap them. I’ve always enjoyed forcefully deleting the wrong words and letters. “No, you don’t belong. Begone.”

    Right now the big open question is how much I will like this keyboard for typing and general use in the long term. Will I get over the mechanics and wish it was quieter? Will I get so spoiled by the feel that other keyboards are hateful in my sight? I don’t know. I really don’t.

    I really do like the super low profile laptop-style keyboards that Apple ships with their computers now, and I’m not sure how much of this is keyboard nostalgia for the days when I spent most of my time in DOS or a Unix terminal, and how much is actual typing speed and comfort.

    Only time will tell. Time and a lot of typing.

    — Steve

  • Drinking my first all-grain batch, and preparing for the next

    My pale ale turned out pretty good. I wish it was slightly hoppier and I think the ESB was better (seriously I love how that one turned out, awesome beer) but it tastes good and is nice and pale and clear. I’d call it a pretty solid success, especially for my first all-grain batch in a cooler mash system I had just built.

    I think I’m going to brew this rye ale I have the ingredients for this week. It should be ready about a week after I bottle the Belgian ale, and then I’ll have 3 beers to choose from in storage (pale ale, rye ale, Belgian ale), and probably ready to drink by June 30. I may need more bottles though. I definitely have enough for the Belgian ale but probably not enough for three full/near full batches.

    It’s OK though, I can just go back to the liquor store and buy some more of these great German hefeweizens that just happen to come in sturdy brown swing-top bottles with easily removable labels. $4 each, empty bottles alone are about $2.50 from a supplier, and the 500 mL beers are easily worth $1.50. The Germans are probably wondering why their bottles don’t come back.

    — Steve

  • Minneapolis Spring 2012

    Despite the big travel shuffle that ended with me changing my plans and attending my brother’s small wedding, I did make it out to Minneapolis. Only one week later than planned, too!

    I really like this town. I like that it is covered in trees. I like that the streets make no sense. I like that so many of the neighborhoods are old. I like the river. I just wish that the weather would cooperate. What a cold and miserable Saturday this is!

    But it’s OK, it’s good to get some time to spend with Ben and Sam. Even if we aren’t the most exciting people any more. Even if we sit on the couch after dinner being sleepy and boring. It’s a great chance to catch up on conversation with good friends. We talk all the time on the internet, but real person to person talk and conversation is rare.

    One of the best parts of the weekend was when Ben and I took Oscar for a walk out by the river, and Ben showed me a little stream fed by a natural spring, and a hidden waterfall the stream flowed over.

    [![Waterfall of Ben][waterfall-sm]][waterfall-lg]

    Liz joined the boys (us) for pizza last night, and then we all gathered back at Ben’s house to relax.

    We also explored the downtown Minneapolis library today, and got some good meat and sausage at a local shop. The plan for tonight is to cook the meat and then brew some beer.

    — Steve

  • Jeff and Diana’s Wedding

    My brother got married last weekend.

    It was a small, informal family wedding, and everyone on both sides made it. Even me. I wasn’t going to go at first. We only had a few weeks notice of the date, and it was on the weekend I had bought plane tickets to visit Ben in Minneapolis. It seemed OK, because I’m going to see them in Atlanta in June, and they plan to do a bigger more formal party and event later. Our family friend Lisa convinced me to go though, and I swallowed the high cost of travel and changed my plans.

    I’m glad I did. With me and Diana’s brother Josh as the last stragglers that made everyone.

    The ceremony was held in a pretty little park, and was officiated by a really cool judge with killer boots who Jeff used to work for and knew him and Diana both. The ceremony was unrehearsed and a little uncertain, with a lot of laughing and figuring it out as they went. It was so much fun, and you can see that on everyone’s face in the photo gallery. It also illustrated how great it can be when the person presiding knows the couple.

    I had a lot more written, but really I’m just very happy that they did this. They’ve been together for around 8 years now, and Diana has been a member of our family for a long time. Now it’s official.

    So congratulations to my brother Jeff and his wife Diana, two really excellent people.

    Jeff and Diana’s wedding photo gallery.

    — Steve