Endo wrote:Having a custom tailored temp and pressure profile for each bean would be like having "electronic contols" on your camera.
No, it isn't. It would be more like (IMHO) having electronic controls on your wine cellar, telling you that Cabernet Sauvignon is ready in 5 years, 4 months and 23 days . . . and then unlocking that bottle from its pre-programmed spot on the rack -- without taking into account the variation in vintages; without taking into account "California" is sub-divided into a myriad of smaller regions that can vary wildly from one another; and without taking into account that
this Napa Valley winemaker specializes in producing Cabernets that
need time to age, whereas
that Napa Valley winemaker focuses on making wines that need very little age . . .
In that scenario, having a pre-programmed "profile" for "Napa Valley Cabernet" would be as useless as having one for "California Cabernet" . . .
Regardless of the time of day, the year, or the geographic location, taking a landscape picture focused out to ∞ in
x amount of ambient light requires
y shutter speed in a digital camera, or
z at ISO ____; whereas at
x-2 ambient light, the camera's programming says the flash is required. That will be a consistent requirement that, yes, can be overridden by the operator (hopefully with sufficient knowledge to do so in such a manner as to improve the quality of the picture!). Using a telephoto lens from the sidelines of a football match requires a different set of programming, but again: light and shutter speed can be programmed in with a high expectation of quality.
Sorry. I am not trying to belabor the point, but I don't see any possibilities for doing this based upon the vagaries of Nature.
A portion of the problems I see could potentially be eliminated if one limited the programing to single-origin coffees
programmed by the estate's name, rather than merely saying "Brazil," "Columbia," or "Yemen" (in other words, standardizing the naming of origin -- like the French
appellation d'origine contrôlée system) Part of the problems might be handled if one can program not only the roast date (in terms of days after roast -- but how does one tell the programming that the beans have been in the freezer for two weeks as opposed to sitting on the shelf at *$ for weeks?), but also the roast level (and again, standardization is crucial). But I cannot see how you deal with the "vintage" differences, or beans that are blends . . .
Cheers,
Jason