Bill Velek <billvelek@[EMAIL PROTECTED]
>:
>First, I'm an experienced all grain brewer, and I have a couple
>of basic brewing books, so I don't need anything to explain how
>to brew, etc.
>Second, I did spend quite a bit of time trying to research old
>threads via Google groups, but most of the threads seem rather
>'dated' -- anywhere from a couple to several years old -- and
>I'm wondering if there is more info and experience out there
>now.
>I use BeerToolsPro software to help me design my recipes, but
>that only provides me with the amounts and temps of strike water
>and infusions, sparge water, etc., along with telling me whether
>my ingredients will result in how many IBUs, color range, and
>original/final gravity, etc., but does not readily tell me, for
>instance, _which_ hops are the most appropriate for a given
>style of beer, etc. I have considered getting one or more
>books, and have some interest in the 'cloning' books, but have
>read in several old threads that they are actually not very
>accurate and very often use grain bills, hops, and mash
>schedules that are at odds with what is known (or commonly
>believed) to be the actual ingredients/schedule for the target
>brews. I am therefore wondering about 'Designing Great Beers'.
>Is anyone here familiar with that book, and would it be a good
>way to supplement brewing software? I know the easy answer is no
>doubt "Yes", but in what way? What I'm looking for is something
>that will tell me that for "this" beer or beer-style, I should
>use "this" type of hops, and "that" yeast, etc. Any info that
>will help be better appreciate "why" certain ingredients are
>used for a particular style would be great, too. If there are
>any other book recommendations, that will be appreciated, as
>well.
I second the "Designing Great Beers" recommendation. Along with
recipe history and analysis, there are good explanation of how to
determine water usage, grainbill, and hop additions. Even if
using brewing software, this stuff is good to know just for
general edification.
cheers,
Scott S
--
Scott Sellers |
scottsellers@[EMAIL PROTECTED]
|
|
