chuggnutt.com

The A-Team movie trailer

Sat, 09 Jan 2010 23:44:25 PST

So the first trailer for this year's A-Team movie hit the net yesterday, and if you follow me on Twitter you know that the first link to it I posted was taken down ("infringing"). But of course you can just search YouTube and find it again if you want to watch it.

...I've watched it a bunch of times now. I can't help it: it looks friggin' awesome, and damn if that isn't a good movie trailer. Now I can't wait for the movie to come out.

Well, yes, I am that geeky.

Two random things

Tue, 05 Jan 2010 23:45:10 PST

Two totally random things today that I found on the internets:

The Oatmeal ASCII art: I have no other commentary other than go to that site and view the HTML source.

Well, I have some commentary. It makes me want to drop ASCII art in the web pages I work on...

Nic Cage as Everyone: Funny and odd. Whomever thought this one up has too much time on their hands... of course. That being said, there are some really good image editing jobs on some of those pictures.

2010

Sun, 03 Jan 2010 23:21:30 PST

The new year is upon us, and we finished off our old year and started up this new one in San Diego. We left a week ago, on Sunday, two days after Christmas, with a mad plan to get up really early and make the drive in one day.

For background, last June when we left San Diego (yes, you counted correctly, that's two SoCal trips in the same year), we left about 7:30 in the morning and managed to get home about 10pm that night—roughly 14.5 hours is the number that sticks in our head.

This time, traveling south—we rolled out at 6:10am and arrived right around 11pm—it took roughly 17 hours. Two things worked against us: snowy roads on southern Highway 97 in Oregon and all the holiday traffic returning to Southern California the same day.

It was grueling.

We spent New Year's Eve at my brother's house, playing Balderdash and Left 4 Dead 2 and drinking beers and ringing in the New Year. We had tired kids, so we retired to our hotel just after midnight.

So far my 2010 has consisted of seeing Up in the Air (my brother and sister-in-law watched the kids for us), drinking more beer, and driving home. We left San Diego around 9am yesterday and made it to Redding around 8pm last night—we wisely decided to split the drive home into two days.

The 11-hour drive to Redding isn't nearly as bad as it sounds; we made really good time most of the way—through Los Angeles especially!—and we stopped for maybe an hour at the Olive Pit in Corning for dinner and, well, to shop for olives.

We made it the rest of the way home by mid-afternoon today, and I'm pleased to report none of the snow and ice we encountered a week ago is there. The roads were perfectly clear and except for some weird inversion-layer fog we hit just out of Weed—and up through Klamath Falls—driving conditions were great.

So, in a nutshell, that's how my 2010 is going so far. How's yours?

Merry Christmas!

Fri, 25 Dec 2009 12:27:07 PST

Christmas wishlists of yesteryear

Sat, 19 Dec 2009 23:42:08 PST

Ah, Christmas. A time to compile lists of desired items in the hopes that someone will get them for you as a gift. I amused myself by thinking up this list of things that made perfect sense to ask for at the time... but today, just seem hopelessly outdated.

I like to think of this stuff as "incidental technology."

VHS Tape Rewinder

Because you don't want to wear out your VCR by rewinding the tapes in it. Or at least, that was what I always heard—hence, the dedicated tape rewinder. Don't forget the ones that look like sports cars!

Floppy disk hole punch

Because it really sucks to have single sided floppy disks—5¼" disks, of course. Now you can make those into double sided disks by making a custom notch on the other side! It certainly beats using a regular hole punch and hoping you don't nick the magnetic part of the disk inside.

8-Track cassette adapter

You have all these cassette tapes but all you have to play music is an 8-track player. Out of luck? Not anymore! With this adapter you can play your cassettes in your 8-track player, saving you the money you would otherwise have to spend on a tape player—or even a stereo!

Tabletop arcade games

The ironic thing is, I remember seeing these in the Sears toy catalogs and thought they would be awesome to have: Coleco's tabletop arcade games were sold in the early '80s and came in the flavors of Pac-Man, Ms. Pac-Man, Donkey Kong, Frogger, and Galaxian. You can read up about the Pac-Man game (with links to the others) here; check out the hot fixed-digital graphic action!

Google's next logo doodle will be of a Terminator

Sun, 13 Dec 2009 23:18:06 PST

Maybe it's just me, but this story on Slashdot about Google developing quantum computing is making me nervous. Why? One word: Skynet.

I have an idea that the first real quantum computer will go "runaway" and develop into a true strong AI—the first sentient computer. It's a science fictional notion, sure, but when they've essentially shown that a quantum computer can run without even being turned on—well, what's science fiction these days?

Twitter and Retweeting

Mon, 07 Dec 2009 23:56:27 PST

I've been thinking a bit lately about Twitter's new "Retweet" functionality. Okay, first of all, there is a scary number of hits when you search "retweet": 9.8 million from Google. That just seems wrong somehow, considering "retweet" is a made up word that's only been in the lexicon for what, a couple of years at most?

Anyway. In short, a "retweet" is when someone copies and re-tweets your Twitter message, usually by putting "RT @username" in front of it. It's a way of sharing something you like with your own Twitter followers and it has become very common practice in the Twitter world.

So common and popular, in fact, that Twitter itself has created a "Retweet" button that they're experimenting with. It's a handy piece of functionality: it copies the Twitter message you like to your timeline so your followers can read it, but instead of looking like it came from you with "RT @username" prepended, it shows the original tweet with a notation that you are the (re)tweet source.

(Obviously I have this Retweet function attached to my Twitter accounts, so I've been playing with it.)

What I like about it is the one-click functionality they've built into it: you don't have to copy a message, scroll back to the top of the screen, type "RT @whatever" and paste the message in—shortening it in case your addition breaks the 140-character limit—and then scroll back to where you were in reviewing your timeline.

However, there's two things this functionality breaks: the ability to modify the original tweet to add your own comment (if there's room), and the "branding" of the retweet.

What do I mean about the branding? Well, consider this: every time I manually retweet a message, it's immediately clear to my followers that the retweet came from me: my image and username are right there, and this is especially handy for people that might be quickly scanning their timelines looking for certain images (people they want to read). With Twitter's built in Retweet function, this is broken; users now see a tweet from a user they may not follow, so they may not immediately assume it's something you recommended.

I'm thinking of this in terms of my Hack Bend Twitter account. In that case @hackbend is definitely a brand I'm pushing, in that I want to build awareness of Hack Bend and ultimately build credibility and drive more traffic back to that blog. When I do a manual retweet, followers can quickly and easily see that @hackbend has posted, and recommends something. With the new Retweet function, they don't immediately see @hackbend, and—if they're looking for Hack Bend-related tweets—they potentially miss it.

So I'm a little on the fence. I think for my @hackbend account, where branding is definitely an issue, I will continue to do the manual "RT @username" retweeting (unless I just get lazy). Otherwise, on my @chuggnutt account, I'll keep playing with the auto-Retweet feature. But I'm curious as to what other people are thinking.

An interesting experiment might be to track which style of retweeting generates more traffic; do a Twitter post in one account, linking to a site (tracking hits from Twitter, of course), and then retweet it in the two different ways in another account. There should probably be various controls, but I'd be curious to see which works better.

The end of November

Mon, 30 Nov 2009 23:41:20 PST

(As I type in the title to this blog post, I have the line "Remember, remember the fifth of November" from "V for Vendetta" running through my head.)

I blink, and November has passed; tomorrow is December 1st which for all intents and purposes heralds the Christmas season. Well, actually according to the Shopping Gods the Christmas season is already in full swing—but I'm slightly more of a traditionalist than that.

Thanksgiving was nice and uneventful: a big meal, lots of beer, and a small group. I always view these holiday weekends to be taken advantage of in a relaxing sense, so what was I doing out the day after Thanksgiving hanging lights on the house in a snowstorm?

Freezing, that's what.

Much of my month has been concerned with beer writing (the parts that aren't concerned with work, and family, and so on): I'm gearing up for the Advent Beer Calendar which starts tomorrow on the Brew Site, and I've been signed on as a Featured Writer for RateBeer's new Hop Press group blog.

Meanwhile, I actually have some posts queued up in my head for this poor blog here. Maybe over the next few days I'll actually get them written.

NaNoWriMo (manageably)

Tue, 03 Nov 2009 22:39:55 PST

No, I'm not actually participating in National Novel Writing Month, but I toyed with the idea (again), and in doing so I did some back-of-the-envelope calculations to see how manageable it would be. The results were interesting, so I thought I'd share.

The idea, of course, is to write a 50,000 word (minimum) novel in the 30 days of November. Breaking that out by day, you have 1,667 (rounded up) words per day to complete.

1,667 words per day doesn't seem all that daunting, but once you sit down and start writing some out you start to realize how many it actually is. So let's borrow a page from algorithm design in computer science and break it down into smaller, more manageable chunks.

In particular, would spending say, five minutes each hour of your day writing be manageable? Yes? Doesn't matter which five minutes, just as long as you open your text file or Word document or Google Docs account and write however many words you need for five minutes.

So if five minutes each hour works, let's figure out how many words you'll need to write for each brief session. In order to determine that, we need to figure out how many writeable hours you have each day. The number I fell upon was 15: assume you wake up and/or are functional by 7am, and can finish sometime in the 9pm hour. That sounds reasonable, right?

So dividing 1,667 by 15 yields 112 (again, rounded up). That's how many words you have to write each hour for the 15 workable hours you have each day of November to reach 50,000 words and thus a novel.

Can you write 112 words in five minutes? I'm able to hit that in about two, but of course that isn't necessarily stringing together meaningful prose, or at least something somewhat resembling a coherent narrative. But even if what you write is dreadful, at least you're writing something.

Spending five minutes each hour to write 112 words? Seems laughably easy! How couldn't you find the time?

Happy Halloween

Sat, 31 Oct 2009 16:56:23 PST

Happy Halloween everyone! Hope you all have a safe trick-or-treating (or whatever it is you do) and thoroughly enjoy the day.

And because it's Halloween I couldn't resist running a few of the various weird images I've posted over the years. Enjoy!

I've been in the newspaper 3 times now. I think.

Tue, 20 Oct 2009 23:52:34 PST

I was in our local Bend Bulletin today, in an article about seasonal beers. Nice article, mostly accurate, but I was very surprised by the amount of "screen time" I got, so to speak. I only spoke with the reporter for something like 10 minutes on the phone last week.

This makes the third time that I've "officially" been in the paper, as an interviewee; the first was for a story on blogging back in 2004, the second was just last year (also on blogging).

But unofficially, I may have been mentioned without my prior knowledge, so it could (sort of) be more than three times: for instance, my blog was quoted (giving attribution to me) back in 2005 but I didn't know about it until after the fact.

Thank goodness I come across lucid in today's article, though. Sometimes I'm in those interviews and I just feel like I'm rambling nonsense.

A book I'd like to read

Sun, 11 Oct 2009 23:24:51 PST

A few years back, Law & Order had an episode where the killer planted a body part in the wreckage of the World Trade Center so that the crime would be covered up, looking instead like collateral damage from 9/11. It almost worked (but didn't, of course) and got me thinking that the same type of plot device could be used in a different historical context, for instance the London Blitzkrieg during World War II.

So of course I began working the idea around in my head: a body is found in the rubble of a London building, and it turns out to have been planted there to cover up a murder. But since I've very little experience reading detective fiction I've decided that rather than trying to put that idea to paper myself, some writer out there must already have tackled the subject of mystery fiction set during World War II London. And I'd rather like to read it.

So, the question: does anyone know of such fiction, and/or could point me in the right direction? (Besides Amazon and Google searches, I mean. I'll do that too, but those are no substitutes for actual recommendations.)

Bloggers must disclose payments for reviews

Mon, 05 Oct 2009 23:58:34 PST

As a blogger who receives samples of products (mostly beer) and writes reviews of them, I read with interest this story that popped up on LATimes.com today: Bloggers must now disclose if they got paid to write a review.

Basically, the Federal Trade Commission has revised their "Guides Concerning the Use of Endorsements and Testimonials in Advertising" to add specific rules and language concerning bloggers.

A blogger who reviews a product — but leaves out the fact that he or she got a payment, high-value gift or free vacation to write the review — could run afoul of new federal regulations on advertising.

"The post of a blogger who receives cash or in-kind payment to review a product is considered an endorsement," said the agency in a release. "Thus, bloggers who make an endorsement must disclose the material connections they share with the seller of the product or service."

A blogger can, however, accept a free sample of a product for review purposes without disclosure, "provided that the product itself does not have such a high value that would make its receipt material (e.g., a car)," according to the revised rules.

I'm surprised I haven't seen more being made of this online yet; this should be a big story in the blogosphere. These changes go into effect December 1st.

Fortunately I disclose everything that I've received on behalf of my blogs (really only The Brew Site has generated anything), and just as fortunately, while I've received lots of samples, I haven't accepted any money or high-value material payment to do so. (I've received various bits of glassware with some of the beer, but that's it—and it's all documented on the blog.)

I'm going to be very interested to see how this shakes out the blogging world. Kids, disclose those payments!

The year of harvest

Fri, 02 Oct 2009 23:35:18 PST

This year, or the latter half, at least, has been a big harvest year for us. And one of the things that goes along with harvesting your own produce (or whatever) is the packaging and storage: you don't want the stuff you picked to go bad. So there's been a lot of freezing and canning this year as well.

This is the first time I've ever canned, believe it or not. Me personally, I mean; my mother canned all sorts of things when I was growing up. But having never done it myself, it was always a bit mysterious as to the process; turns out, it's very, very easy. Most of the work comes in processing the fruit before it even hits the jars.

Check it out:

Our July trip to Hood River yielded a bunch of cherries and blueberries: about 12 pounds of the former and about three pounds of the latter. We vacuum-sealed and then froze them.
Between my small hop vine and the hops at my parents' place, I picked several pounds of hops, which yielded something like 11 or 12 ounces of dried hops. Which I'll be brewing the next several batches of beer with.
The four pounds of wild plums from my parents' place that I blogged about yesterday is yielding one gallon of wine.
Another fruit-picking trip to Hood River a couple of weeks ago netted us about 130 pounds of apples and pears. Literally. Plus we brought home 12 or so pounds of peaches. The peaches went into freezer jam, and I've made (and canned) applesauce, canned four quarts of sliced apples, and eight quarts of halved pears. So far; there is still a lot of fruit to go.
Three nice tomato plants were very productive.
Our small garden this year (which was flooded out by torrential rains in the spring) yielded a number of carrots, onions, and a bit of lettuce; one medium-sized pumpkin (which is still on the vine as of this writing), and even one very small watermelon!
I have a giant bulb of fennel from my mom's garden. And come to think of it, several pounds of frozen rhubarb from her garden earlier in the year, too.

There's more canning to be done this weekend, and I'm also thinking up other things to possibly do with the pears and apples—but since my creativity in this area tends to run towards alcohol, what I've come up with is apple/pear beer and pear wine. Perhaps a pear vodka sounds interesting too.

Oh, I was thinking about making some apple butter also.

And I've been making more beer this year, I suppose that counts. In fact, I have two five-gallon batches in carboys ready to bottle (likely this weekend), and if I want to brew with the fruit I should probably have another batch going soon.

Our house has become so domestic...

Plum wine

Thu, 01 Oct 2009 23:51:43 PST

At my parents' place in Alfalfa, they have a wild plum tree that produced fruit for (I believe) the first time ever this year. They were small, golden fruits that were terrifically sour as they grew, but ripened and turned a deep pink-purple and ended up being rather sweet.

They picked a bunch of the plums, and then picked a bunch more for me (at my request): I ended up with almost four pounds of them, many very ripe! I debated for a bit on what to do with them and decided to make wine.

I found a plum wine recipe online and went with it (the "basic" recipe at the top of the page); for a gallon of wine, it calls for three to four pounds of plums which worked out just right (four for sweet plums, three for wild—I compromised and used all four-ish pounds). The pitting of the plums was the biggest chore, as many were (over)ripe and almost falling apart, and many others were very small. The rest went fairly smoothly: making wine is easy.

That was about a week ago, and I racked it from the bucket to a gallon-size glass jug tonight for secondary fermentation. I'll rack it again in about three weeks, and then again about three months after that. Then, of course, I'll bottle it and (according to this particular recipe) age it for another six to 12 months.

(Making wine is easy—I didn't say it was quick!)

No idea how the final product will turn out, but I did taste the sample I drew for the hydrometer reading: still fizzy with fermentation and a bit yeasty (especially the smell), it was fairly sweet and—if not for the yeastiness—would make a tasty drink right now.

Nothing to do now but shove it away in the the closet and be patient.