…and one more thing…

Guess what…

Remember that picture from yesterday? I strategically cropped out what was written on the shirt. 🙂

Brooke’s pregnant again! No idea what the gender is yet (boyboyboyboyboyboyboy…), but the due date is September 21st, 2013 and all is well with Mom and baby.

Well, maybe not with “Mom,” as much.  She’s taken to a bit more “morning sickness” (read: all day sickness) than she did when she was pregnant with Meg, but hopefully as the first trimester draws to a close, that’ll start to subside a bit.

Still, we’re excited to add to the family!  And Meg’s excited to be a Big Sister. 🙂

Meg Turns 3!

What a difference three years makes!
What a difference three years makes!

Meg is three today!  I thought it would be nice to put up the “comparison shot” just to show how much she’s grown in the past 3 years.  I can still see some similarities in the two pictures (especially in the nose), but she’s pretty different now!

We had some folks over for a birthday party on Saturday – a “Fiesta”-themed party this year.  Meg is very much into Dora The Explorer, so while we didn’t want to specifically theme it around that bastion of consumerism, we still wanted to make it center on her interests.  That, and a “fiesta” theme work swell for margaritas and Mexican beer.

Brooke devised an activity for the kids to do (we had 3 other toddlers in the house that day, among 20 people in total…full house!!) where the kids went “on an adventure” (like in a Dora episode…), going “over the lake,” then “up the ‘stair’ mountain,” then “dancing,” then finally to a box of “treasure” including maracas and stickers for them to all play with.  We also had sombreros available for the kids (and certain adults).

Overall, a good party for her, methinks!  She doesn’t quite get that her birthday party wasn’t on her actual birthday yet, but we’ll get there.  Spreading it all out over a few days is likely a bit confusing, as she probably thought she was now three on Saturday instead of today.  Oh well.

Still, Meg got a dollhouse this morning, opened a few more small things, and we’ll go out to Uncle Bill’s Pancakes tonight for dinner – that girl loves her pancakes. 🙂

Happy birthday, Margaret Jean!

Review: House of Cards

House of Cards (2013

Netflix is playing a very interesting game lately, not only continuing to swipe content typically reserved for cable television, but also dipping their toes into exclusive first-run content the likes of which only the HBOs and Showtimes of the world get access to.  House of Cards is the second of these series (and actually a re-make of an early-90s BBC production), following Lilyhammer (which I haven’t seen), and will be joined soon by their third offering, another season of Arrested Development (and believe you me, Brooke and I are excited about that one…).

House of Cards, specifically, is the product of Netflix’s enormous data mining initiative.  Everything you watch, they pay attention to.  They know how often you pause during a show, how often you repeat a given segment (and which segment), and how everything you like relates to one another.  Case in point, courtesy of Salon: “Netflix subscriber viewing preferences clinched [the] decision to license a remake of the popular and critically well regarded 1990 BBC miniseries. Netflix’s data indicated that the same subscribers who loved the original BBC production also gobbled down movies starring Kevin Spacey or directed by David Fincher. Therefore, concluded Netflix executives, a remake of the BBC drama with Spacey and Fincher attached was a no-brainer, to the point that the company committed $100 million for two 13-episode seasons.”

Greenlighting the series for two seasons from the beginning allows production to plot an outline for those seasons from the very beginning (with, of course, the ability to opt for more depending on performance).  Creatively speaking, this is very attractive, as most networks won’t guarantee you more than a season (or a few episodes) from the outset.  This kind of freedom was helpful in attracting David Fincher to the series, who served as Executive Producer and directed the first two episodes.  If you don’t know who Fincher is, you should recognize his work as director of The Social Network, The Girl With The Dragon Tattoo, Se7en and Fight Club (not exactly a “nobody”).

House of Cards focuses on Congressman and Majority Whip Frank Underwood (Kevin Spacey), who is passed up for the Secretary of State nomination by the newly-elected President in the first episode.  The series focuses on Underwood’s sophisticated plotting as he and his wife, Claire (Robin Wright), seek revenge against those that wronged him.  In many ways, he’s playing a long chess match, where he’s always looking many moves ahead until “checkmate” is within his grasp.  The relationship between Frank and Claire is a complicated one, where each has their own interests that serve each other’s purpose at any given time, further complicated by favors and lobbying that pull them apart (and back together).  All the while, you sense they care deeply about each other, perhaps not necessarily as “husband and wife,” but more as teammates determined to achieve the same goal(s).

The acting is unbelievable, especially between Spacey and Wright.  By the end of that season, you know that Frank and Clair, both individually and together, are capable of doing just about anything to get what they want.  You’ll recognize a host of actors in the series, and they’re all superb.  I had no idea who Corey Stoll was before this show, but geez, he convinced me he’s a drug-addicted congressman, or at least knows one in real life.  Kate Mara is an actress I wasn’t particularly familiar with, but certainly did a great job in her own right.  Spacey and Wright, however, are the two that steal the show.  They both deserve Emmy nominations, though apparently, Netflix doesn’t count as “broadcast television” and may be ineligible.

The hype leading up to the release of the series was coincident with various articles discussing how to even talk about it, as there are no general “rules” for spoiling “last night’s episode” at the water cooler for those that haven’t seen it.  Conceivably, anyone that had 13 hrs to blow on the first night of release could have seen all of it before going in to work.  By most accounts, House of Cards is performing well, however. Though Netflix won’t release specific numbers, it’s apparently the most-watched “thing” on Netflix in 40 countries.

I’ll definitely be back for season 2.  And so should you.

Aftermath

15 gal, ready to go.
15 gal, ready to go.

As I mentioned last week, I wanted to make some beer for Kristen’s wedding, coming up in July.  In order to ensure the beer gets produced on time and that I can taste it and produce more if the first batch doesn’t work out, then a February start-date for fermentation is required.  Thus, with the help of Mom, Dad and Brooke, I set out this past Saturday to make lots o’ beer.

This is the first time I tried making this much in one day.  I’ve tried two batches in a day before, but one of them didn’t work out as well (for various reasons, not just because I tried two in a day).  Regardless, having all the additional help available to keep Meg occupied and watch the boiling kettle while I take care of cleaning the carboys, etc. is very useful and makes the day go more smoothly.

Overall, the day went pretty well.  I used up one of the propane tanks I had, so Dad and I went and got another one mid-way through the day.  Once the sun poked out, the weather got a bit more comfortable, though it was only out for a few hours before going behind the house, leaving us in the shade with a brisk, chilly wind.  Dad assembled Brooke’s new IKEA 3-drawer dresser while we brewed the second batch later in the afternoon, so we kept ourselves busy.

After we went out to dinner, I went ahead and took care of the third brew on my own (though Brooke held the funnel for me so I could pour the wort into the second carboy).  All in all, it ended up taking about 11 hrs, start to finish, to do the three beers with a few hour+ long breaks in there.  I’d guess that the act of brewing, itself, “only” took 6-7 hrs.

IMAG0178_0
Active fermentation warrants blow-off tubing, especially in carboys.

The beers were all pretty close to the target original gravity, so I expect the final alcohol content to arrive at a similar level to the first time I did these beers.  Fermentation began relatively quickly and, as you can see in the image above, the limited headspace in the carboys required the addition of blow-off tubing to allow the foam to escape.  I can probably remove the tubes in a few days.

In about two weeks, I’ll dry-hop the Chinook IPA, which was put in the bucket specifically so dry-hopping wouldn’t be a huge pain.  It can be done in the carboys, but getting the hops in there, wrapped in cheesecloth, and then removed again from the carboy can be difficult.  After another week (so, 3 weeks total in the fermentation vessels), I’ll bottle the beer.

Now that will be time-consuming.  I’ll probably queue up something to watch on the Kindle while I take care of that.

Regardless, the day was a success!  Hopefully the flavor reflects that in a few months. 🙂

Projects

Beer...

So, my little sister is getting married in July and I offered to make a contribution of homebrew to the festivities.  She’s going to design labels for them and will make them available as people leave the reception, rather than making it available during the reception, which would require us to deal with some logistical hurdles…and make a lot more…

Regardless, I picked two of the better varieties I’ve made before.  The Cream Ale batch I made was light, highly drinkable, and can be enjoyed by folks with a range of tastes, including those with only a taste for yellow fizzy water (e.g. Bud Light).  The Chinook IPA is something quite a bit different, as it is a hoppier pale ale.  It probably won’t suit as many tastes, but will still allow for some variety between beer styles.  Kristen’s fiancé, Jake, who has also started homebrewing recently, will make a batch of something “in the middle,” so perhaps something like a honey brown, for example, or a wheat beer.

In total, we should end up producing around 20 gal of beer which, assuming we actually got that volume (and we won’t), would net 213 bottles.  Not too shabby.

Part of doing the brewing now, though, is to ensure the beer is actually somewhat decent.  I’ll bottle it in early-March, and it can then condition and age into April.  If it isn’t great (or at least good) by April, then I can brew some more and still have it ready by mid-July.  I don’t want to take any chances in beer quality here: I don’t mind drinking my own batches I’ve screwed up, but I wouldn’t want to impart them upon others.

Still, this Saturday, I’ll brew 15 gal of beer, all in one day.  I’ve done two batches in one day before, but this will be the first time I attempt three.  Mom and Dad are going to drive in to help out (and by “help,” I mean entertain a certain almost-3-year-old so I can focus on making 15 gal of beer).  The forecast says that it should be 47 F and partly cloudy, so likely a pretty good day for some outdoor brewing.

#firstworldproblems

Here's the replacement...
Here’s the replacement…

A few weeks ago, on a Thursday night, I was playing XCOM on my Windows box.  Everything was running smoothly, no problems.  On Friday, I got home and turned on the computer to listen to some music and, for some odd reason, the hard drive wasn’t detected.  As in, the hard drive containing the Windows OS wasn’t even there, so far as the system was concerned.

Thankfully, I only stored Windows and some replaceable programs on the drive that failed (an SSD), and my pictures, music, and videos were all stored on a separate hard drive (a traditional HDD).  Typically when one uses an SSD (or “solid state drive”), you only run programs on it as they can take advantage of the speeds afforded by SSD technology, while slower traditional hard drives (“HDD”) are just fine for other stuff.  So really, all I lost in the drive failure were a few programs (that I could re-install) and some game save files (or so I thought…).

Also, thankfully, the drive was still under warranty.  I’ve had it for less than a year, so I contacted the manufacturer, sent the drive in (last Tuesday) and got the replacement (last Saturday), which is a pretty quick turn-around.  On Saturday, I spent my time re-installing the drive and getting some of those programs back on, but this time, I installed Windows 8 rather than Windows 7 (hey, if I’ve got to re-install everything, I may as well try out the new hottness, right?).  Microsoft is trying to get everyone to upgrade, so they’ve had it on sale for $40, which is a pretty good deal compared with the regular price of $120 (which Win8 will return to after January 31st).  I may write more about Windows 8 later but, for now, it’s “alright.”  My mind isn’t blown.  If you’ve got Windows 7, you’re fine sticking with 7, but 8 isn’t horrible (and it boots really fast).

I mentioned that I lost a few game save files, and this was the worst part of the experience.  I’d put about 9 hours of time into XCOM since picking it up months ago, so I wasn’t looking forward to having to repeat the lost time.  Also thankfully, the program I use to manage the game (Steambacked the save files up to “the cloud,” meaning that once I re-installed the program, my save files were also re-downloaded and restored.

In the end, I lost nothing except for a week of using my Windows-based computer.  All in all, not a bad deal.  And we had the Linux box (that this site runs on…) to use in the meantime.

As a side-note, having no Windows PC to use, and thus, no computer to run iTunes, I couldn’t update my iPod for listening to podcasts during that week.  Instead, I relied upon my cell phone (an HTC One X) for downloading new podcasts and music.  To be honest, I kinda don’t want to go back to the iPod.  I’ve gotten used to downloading podcasts and music immediately from work (or wherever), rather than waiting to go home, turn on the Windows PC, download the podcast or music to the computer, then transfer it to the iPod: it’s much easier to just do it directly.

Unfortunately, I don’t have a way to use my phone in my car, except for relying on the phone’s speakers (which aren’t really loud enough).

Oh well.

#firstworldproblems

01.01.13 Breakfast

New Year’s Day dinner: black eyed peas and quiche. I have no evidence, but I’m pretty sure that quiche has become a New Year’s Day tradition in our house to use up Christmas leftovers.

010113

12.09.12 Dinner

This is from mid-December, but fairly typical of the meals we’ve been having around our house recently. Add a bowl of soup, and you get the picture!
12.09.12

Review: The Hobbit – An Unexpected Journey

The Hobbit

In an effort to express my “anticipation level” for this movie, let me first point out that I read the book, “The Hobbit,” for the first time this Fall, and I re-watched the “extended edition” versions of “The Lord of the Rings” trilogy over Christmas Break (about 11 hours of content, give or take).  It’s about as “prepared” as I could get.  Having just read the book, I was at a loss to explain how exactly they were going to turn a relatively short book into another three movies.

Surprisingly, “The Hobbit: An Unexpected Journey” didn’t really feel all that long to me.  Yes, it’s longer than it needs to be (running time is 169 min), but I’m honestly surprised that it gets you about a third of the way into the book, while also “filling in some gaps” that are left out, in tying it more closely with “The Lord of the Rings” (henceforth referred to as “LotR”…).

Perhaps I should back up a step.   “LotR” covers the adventures of a hobbit, Frodo Baggins, and his crew as they attempt to destroy the Ring of Power so it cannot be used by the evil Lord Sauron to take over Middle Earth.  Frodo obtains this ring from his uncle, Bilbo Baggins, but we aren’t really told how he got it, except that another character, Gollum, had it before Bilbo and desperately wants it back.  The book, “The Hobbit,” was actually published almost 20 years before “LotR,” and it contains the back story for how Bilbo got the Ring.  In movie form, it’s being presented as a prequel, even though  the book was actually published long before.

To be honest, going through the story here isn’t going to be all that interesting.  It follows the book, but also includes a few additional scenes with actors from “LotR,” including Ian Holm and Elijah Wood, and others from the movies.  Unfortunately, in this case, they’re looking quite a bit older than they did in “LotR” (perhaps I did a disservice by re-watching them a few weeks ago…), even though in this film, they’re shown prior to the events of “LotR.”  Ian McKellen also looks remarkably older, despite the presence of a huge beard, though it’s worse in some scenes and barely noticeable in others.

Generally speaking, the acting was great, the pacing was slow at times, but was far better than I expected, and the effects were spectacular.  Seriously, they were good 10 years ago, but it’s noticeable how far the technology has come to the point where CGI and “real life” blend together better than before.  Again, there really isn’t anything special to mention here as, if you saw the previous movies, you should know what to expect.  Though, I should note that the CGI work on Gollum is pretty spectacular, and has really come a long way in 10 years.  I’ve read some complaints (in relation to the “48 fps” debate…) about the quality of the makeup and the props though, personally, I didn’t think the effects in that regard were that bad.  Maybe here and there, but certainly not offensive.

We saw the movie in 48 fps IMAX 3D, which is something of an “experiment” in modern filmmaking.  Briefly, most movies are filmed/shown in 24 fps (“frames per second”), so this movie was filmed in twice that.  This change has the effect of displaying more images to your eyes in the same amount of time, making all the motion look smoother and more vibrant, but also having the side-effect of losing “motion blur” that is sometimes helpful in disguising “plastic-y” looking props.  Needless to say, film critics either love or hate this, depending on who you ask.  If you ask me, I didn’t notice anything bad about it, yet then again, I was watching the movie “as the director intended.”  It was good 3D, it didn’t hurt my eyes or give me a headache, and I thought the 3D effects were added in sparingly, yet effectively.  If anything, 3D should be easier on your eyes at this frame rate.  You don’t need to see the movie in 3D to enjoy it, but for my part, I just wanted to see it at 48 fps and see what the fuss is all about.

If there’s any problem I’ve got with “The Hobbit,” it’s that the story didn’t really “grab” me.  I could say the same thing about “Fellowship of the Ring,” the first movie of the previous trilogy, but I think part of the reason is that, during that first viewing, you’re trying to keep track of a lot of characters at one time.  At least in “Fellowship,” they were pretty distinct and easy to remember (e.g. the elf, the dwarf, the ranger, the wizard, etc.).  In this movie, they’re almost all dwarves, and I couldn’t tell you what any of their names are.  Granted, there are only a few people you’re “supposed” to care about at this point, but some of those dwarves get a bit more focus later on in the book.  We’ll have to see how it plays out, and I can’t see how they could avoid this problem, but it deserves mention.

In the end, I’m glad I saw it and I’m glad I saw it in 48 fps 3D.  Is it better than the movies from the previous trilogy?  Hard to say, without the next two movies available to get the full comparison.  The first movie of the previous trilogy was the weakest of the three, in my opinion, and it could very well hold true for this one as well.

But if it says anything, I’m still looking forward to the next one.

The Holidays

Brooke had to hold Meg's arm still for this one...
Brooke had to hold Meg’s arm still for this one…

To be honest, I haven’t been posting all that much recently because I haven’t had much to say. At the same time, it’s been pretty busy, for one reason or another. With Christmas falling in the middle of the week, I feel like my schedule has been thrown radically off course for the past few weeks, and am only just now getting back in the swing of things.

Christmas was good, of course.  We went to Louisiana, MO for the Baumann (extended) family Christmas on Sunday the 23rd, then continued north to Hannibal for the Baumann (immediate) family Christmas on the 24th.  It was odd seeing how much snow was on the ground up there, as we really hadn’t gotten any in St. Louis beforehand.  At the very least, it still felt like we got a “White Christmas” out of the deal.  After that, we attended our traditional Christmas Eve service back in Louisiana before heading down to St. Louis that night, so that Meg could open her presents under her own tree on Christmas morning.

However, since we didn’t get home until 10:00 pm on Christmas Eve, Meg was quite content to stay in bed until 8:00 am the next morning, meaning we had to wake her up to get her to church on Christmas Day (thus, leaving Meg enough time to open one present before leaving).  Still, it all worked out.  Meg wanted to play with everything she opened immediately, rather than waiting until after everything was opened to choose something to play with.  Perhaps it was better to only get one first.

“Pez? What’s a ‘Pez’?”

We typically don’t go to Christmas Day services, but as we were in town, didn’t have to go anywhere, and our new pastor wanted to have a service on that day (we usually don’t), we went along and had a good time.  There were even some folks in pajamas, bringing a good “family atmosphere” to the proceedings.  It was a short-ish service, but was nice to participate in.

Brooke went to work the next few days, and Meg went to school.  I, being the lazy one, stayed home, getting a few things done while watching the Extended Editions of “The Lord of the Rings” (in preparation for “The Hobbit,” which I still haven’t seen!).  I assembled Meg’s new “big girl bed” (which she’s now sleeping in, most nights), hung out with a few friends, kept up on laundry, etc.  Overall, a good mix of productivity and laziness, so I was satisfied!

We then went to Columbia last Friday for the Linsenbardt (immediate) family Christmas.  Jake and Kristen couldn’t get there around Christmas, so this is the first year I can remember where we pushed things off a few days.  In the end, it was probably better this way as we didn’t feel as rushed, traveling between towns without much lag time.  Still, we had a good time and got to hit up Flat Branch and Shakespeare’s while we were there (making it more than worth the trip).

Always need more Sesame Street books!
Always need more Sesame Street books!

Meg stayed in Columbia with my parents while Brooke, Edie and I returned to St. Louis for New Year’s.  Brooke actually went in to work for a little bit on New Year’s Eve while I took down the tree and did a few other things around the house.  We hung out with Adam and Kelley that night, which was rather nice because we typically have them over to our house (as Meg is usually in bed by 7:30, and they live 20+ min away from our house, making dinner a difficult prospect).  Regardless, good food and good times with friends, so it was a nice way to ring in 2013.

And now, I’m back at work.  I had a good time over break, but am ready to get back to a typical routine, even if it means getting up “early” and putting clothes on instead of staying in PJs all day.  We won’t have any easy weekends coming up, though, as my cousin gets married on Saturday (the bachelor party is tonight, and the rehearsal is tomorrow…I’m an usher and Meg’s flower girl-ing…), so we’ve got our work cut out for us.

But thankfully, Cabin Fever is next Saturday.  Can’t wait for that one. 🙂