Category Archives: comment-fishing

Profils et web social

J’écrivais ce message à un ami, à propos de mon expérience sur le site xkcd.com.

 

What? Oh, no, the 'Enchanted' soundtrack was just playing because Pandora's algorithms are terrible. [silence] ... (quietly) That's how you knooooooow ...
BD de xkcd
C’est sur xkcd, mais ça pourrait être ailleurs. C’est rien de très spécial, mais ça me donne à penser à ce qu’est le vrai web social, en ce moment. Surtout si on sort de la niche geek.

Donc…

  • Je vois le dernier xkcd.
  • Ça me fait réagir.
  • Je veux répondre.
  • Je sais qu’il y a des forums pour accompagner ces bande dessinées.
  • Je vais sur le forum lié à celui-ci (déjà quelques clics et il fallait que je connaisse l’existence de tout ça).
  • J’appuie sur Post Reply
  • Ça me demande de m’identifier.
  • Comme je crois avoir déjà envoyé quelque-chose là, je me branche avec mon username habituel.
  • Ah, mauvais mdp.
  • Je fais “forget pw”.
  • Oups! J’avais pas de compte avec mon adresse gmail (faut que ça soit la bonne combinaison donc, si je me rappelle pas de mon username, ça marche pas).
  • Je me crée un nouveau profil.
  • Le captcha est illisible, ça me prend plusieurs tentatives.
  • Faut que j’aille sur mon compte gmail activer mon compte sur les forums xkcd.
  • Une fois que c’est fait, je me retrouve à la page d’accueil des forums (pas à la page où j’essaie d’envoyer ma réponse).
  • Je retrouve la page que je voulais.
  • J’appuie sur Post Reply.
  • J’écris ma réponse et je l’envoie.
  • Évidemment, mon profil est vierge.
  • Je vais modifier ça.
  • Ça commence par mon numéro ICQ?? Eh bé!
  • Plus bas, je vois des champs pour Website et Interests. Je remplis ça rapidement, en pensant au plus générique.
  • Il y a aussi ma date de fête. Pas moyen de contrôler qui la voit, etc. Je l’ajoute pas.
  • J’enregistre les autres modifications.
  • Et j’essaie de changer mon avatar.
  • Il y a pas de bouton pour uploader.
  • Ça passe par une Gallery, mais il y a rien dedans.
  • Je laisse tomber, même si je sais bien que les geeks de xkcd sont du genre à rire de toi si t’as un profil générique.
  • Je quitte le site un peu frustré, sans vraiment avoir l’impression que je vais pouvoir commencer une conversation là-dessus.

Deuxième scénario.

J’arrive sur un site qui supporte Disqus (par exemple Mashable).

  • Je peux envoyer un commentaire en tant que guest.

You are commenting as a Guest. Optional: Login below.

Donc, si je veux seulement laisser un commentaire anonyme, c’est tout ce que j’ai à faire. «Merci, bonsoir!»

Même sans me brancher, je peux faire des choses avec les commentaires déjà présents (Like, Reply).

Mais je peux aussi me brancher avec mes profils Disqus, Facebook (avec Facebook Connect), ou Twitter (avec OAuth). Dans chaque cas, si je suis déjà branché sur ce compte dans mon browser, j’ai juste à cliquer pour autoriser l’accès. Même si je suis pas déjà branché, je peux m’identifier directement sur chaque site.

Après l’identification, je reviens tout de suite à la page où j’étais. Mon avatar s’affiche mais je peux le changer. Je peux aussi changer mon username, mais il est déjà inscrit. Mon avatar et mon nom sont liés à un profil assez complet, qui inclut mes derniers commentaires sur des sites qui supportent Disqus.

Sur le site où je commente, il y a une petite boîte avec un résumé de mon profil qui inclut un décompte des commentaires, le nombre de commentaires que j’ai indiqué comme “likes” et des points que j’ai acquis.

Je peux envoyer mon commentaire sur Twitter et sur Facebook en même temps. Je peux décider de recevoir des notices par courriel ou de m’abonner au RSS. Je vois tout de suite quel compte j’utilise (Post as…) et je peux changer de compte si je veux (personnel et pro, par exemple). Une fois que j’envoie mon commentaire, les autres visiteurs du site peuvent voir plus d’infos sur moi en passant avec la souris au-dessus de mon avatar et ils peuvent cliquer et avoir un dialogue modal avec un résumé de mon compte. Ce résumé mène évidemment sur le profil complet. Depuis le profil complet, les gens peuvent suivre mes commentaires ou explorer divers aspects de ma vie en-ligne.

Suite à mon commentaire, les gens peuvent aussi me répondre directement, de façon anonyme ou identifiée.

J’ai donc un profil riche en deux clics, avec beaucoup de flexibilité. Il y a donc un contexte personnel à mon commentaire.

L’aspect social est intéressant. Mon commentaire est identifié par mon profil et je suis identifié par mes commentaires. D’ailleurs, la plupart des avatars sur Mashable sont des vraies photos (ou des avatars génériques) alors que sur le forum xkcd, c’est surtout des avatars «conceptuels».

Ce que xkcd propose est plus proche du “in-group”. Les initiés ont déjà leurs comptes. Ils sont “in the know”. Ils ont certaines habitudes. Leurs signatures sont reconnaissables. L’auteur de la bd connaît probablement leurs profils de ses «vrais fans». Ces gens peuvent citer à peu près tout ce qui a été envoyé sur le site. D’ailleurs, ils comprennent toutes les blagues de la bd, ils ont les références nécessaires pour savoir de quoi l’auteur parle, que ça soit de mathématiques ou de science-fiction. Ils sont les premiers à envoyer des commentaires parce qu’ils savent à quel moment une nouvelle bd est envoyée. En fait, aller regarder une bd xkcd, ça fait partie de leur routine. Ils sont morts de rire à l’idée que certains ne savent pas encore que les vraies blagues xkcd sont dans les alt-text. Ils se font des inside-jokes en tout genre et se connaissent entre eux.

En ce sens, ils forment une «communauté». C’est un groupe ouvert mais il y a plusieurs processus d’exclusion qui sont en action à tout moment. Pour être accepté dans ce genre de groupe, faut faire sa place.

 

Les sites qui utilisent Disqus ont une toute autre structure. N’importe qui peut commenter n’importe quoi, même de façon anonyme. Ceux qui ne sont pas anonymes utilisent un profil consolidé, qui dit «voici ma persona de web social» (s’ils en ont plusieurs, ils présentent le masque qu’ils veulent présenter). En envoyant un commentaire sur Mashable, par exemple, ils ne s’impliquent pas vraiment. Ils construisent surtout leurs identités, regroupent leurs idées sur divers sujets. Ça se rapproche malgré tout de la notion de self-branding qui préoccupe tant des gens comme Isabelle Lopez, même si les réactions sont fortes contre l’idée de “branding”, dans la sphère du web social montréalaisn (la YulMob). Les conversations entre utilisateurs peuvent avoir lieu à travers divers sites. «Ah oui, je me rappelle d’elle sur tel autre blogue, je la suis déjà sur Twitter…». Il n’y a pas d’allégeance spécifique au site.

Bien sûr, il peut bien y avoir des initiées sur un site particulier. Surtout si les gens commencent à se connaître et qu’ils répondent aux commentaires de l’un et de l’autre. En fait, il peut même y avoir une petite «cabale» qui décide de prendre possession des commentaires sur certains sites. Mais, contrairement à xkcd (ou 4chan!), ça se passe en plein jour, mis en évidence. C’est plus “mainstream”.

Ok, je divague peut-être un peu. Mais ça me remet dans le bain, avant de faire mes présentations Yul– et IdentityCamp.

Actively Reading: OLPC Critique

Critical thinking has been on my mind, recently. For one thing, I oriented an  “intro. to sociology” course I teach toward critical skills and methods. To me, it’s a very important part of university education, going much beyond media literacy.
And media literacy is something about which I care a great deal. Seems to me that several journalists have been giving up on trying to help the general population increase and enhance their own media literacy skills. It’s almost as if they were claiming they’re the only ones who can reach a significant level of media literacy. Of course, many of them seem unable to have a critical approach to their own work. I’m with Bourdieu on this one. And I make my problem with journalism known.
As a simple example, I couldn’t help but notice a number of problems with this CBC coverage of a new citizenship guidebook. My approach to this coverage is partly visible in short discussions I’ve had on Aardvark about bylines.
A bit over a week ago, I heard about something interesting related to “making technology work,” on WTP (a technology podcast for PRI/BBC/Discovery The World, a bit like Search Engine from bigger media outlets). It was a special forum discussion related to issues broader than simply finding the right tool for the right task. In fact, it sounded like it could become a broad discussion of issues and challenges going way beyond the troubleshooting/problem-solving approach favoured by some technology enthusiasts. Given my ethnographic background, my interest in geek culture, and my passion for social media, I thought I’d give it a try.
The first thing I noticed was a link to a critique of the OLPC project. I’ve personally been quite critical of that project, writing several blogposts about it. So I had to take a look.
And although I find the critical stance of this piece relatively useful (there was way too much groupthink with the original coverage of the OLPC), I couldn’t help but use my critical sense as I was reading this piece.
Which motivated me to do some Diigo annotations on it. For some reason, there are things that I wanted to highlight which aren’t working and I think I may have lost some annotations in the process. But the following is the result of a relatively simple reading of this piece. True to the draft aesthetics, I made no attempt to be thorough, clean, precise, or clear.
http://www.miller-mccune.com/business_economics/computer-error-1390.print
http://www.miller-mccune.com/business_economics/computer-error-1390.print
  • appealing
  • World Economic Forum
  • 50 percent of staff were being laid off and a major restructuring was under way
    • The dramatic version which sends the message: OLPC Inc. was in big trouble. (The fact that it’s allegedly a non-profit is relatively irrelevant.)
  • the project seems nearly dead in the water
    • A strong statement. Stronger than all those “beleaguered company” ones made about Apple in the mid90s before Jobs went back.
  • And that may be great news for children in the developing world.
    • Tadaa! Here’s the twist! The OLPC is dead, long live the Child!
  • lobbied national governments and international agencies
    • Right. The target was institutional. Kind of strange for a project which was billed as a way to get tools in the hands of individual children. And possibly one of the biggest downfalls of the project.
  • Negroponte and other techno-luminati
    • Oh, snap!
      It could sound relatively harmless an appellation. But the context and the piece’s tone make it sound like a rather deep insult.
  • Innovate
    • Ah, nice! Not “create” or “build.” But “innovate.” Which is something the project has been remarkably good at. It was able to achieve a number of engineering feats. Despite Negroponte’s repeated claims to the contrary, the OLPC project can be conceived as an engineering project. In fact, it’s probably the most efficient way to shed the most positive light on it. As an engineering project, it was rather successful. As an “education project” (as Negroponte kept calling it), it wasn’t that successful. In fact, it may have delayed a number of things which matter in terms of education.
  • take control of their education
    • Self-empowerment, at the individual level. In many ways, it sounds like a very Protestant ideal. And it’s clearly part of the neoliberal agenda (or the neoconservative one, actually). Yet it doesn’t sound strange at all. It sounds naturally good and pure.
  • technology optimists
    • Could be neutral in denotation but does connote a form of idealistic technological determinism.
  • Child
  • school attendance
    • “Children who aren’t in school can’t be learning anything, right?”
  • trending dramatically upward
    • Fascinating choice of words.
  • tens of millions of dollars
  • highly respected center
    • Formulas such as these are often a way to prevent any form of source criticism. Not sure Wikipedians would consider these “peacock terms,” but they don’t clearly represent a “neutral point of view.”
  • they don’t seem to be learning much
    • Nothing which can be measured with our tools, at least. Of course, nothing else matters. But still…
  • international science exam
    • Of course, these tend to be ideally suited for most learning contexts…
  • There’s no question that improving education in the developing world is necessary.
    • Although, there could be a question or two about this. Not politically expedient, perhaps. But still…
  • powerful argument
    • Tools in a rhetorical process.
  • instinctive appeal
    • Even the denotative sense is polarized.
  • precious little evidence
    • Switching to the “studies have shown” mode. In this mode, lack of proof is proof of lack, critical thinking is somewhat discouraged, and figures are significant by themselves.
  • circumstantial evidence
    • The jury isn’t out, on this one.
  • co-founder of J-PA
    • Did Esther co-write the article? Honest question.
  • the technology didn’t work any better than a normal classroom teacher
    • A very specific point. If the goal of tool use is to improve performance over “regular teaching,” it’s a particular view of technology. One which, itself, is going by the wayside. And which has been a large part of the OLPC worldview.
  • the goal is improving education for children in the developing world, there are plenty of better, and cheaper, alternatives.
    • A core belief, orienting the piece. Cost is central. The logic is one of “bang for the buck.”
  • the teachers simply weren’t using the computers
    • We’re touching on something, here. People have to actually use the computers for the “concept” to work. Funny that there’s rarely a lot of discussion on how that works. A specific version of “throwing money at a problem” is to “throw technology at” people.
  • few experimental studies to show a positive impact from the use of computers
    • Is the number of studies going one way or another the main issue, here? Can’t diverse studies look at different things and be understood as a way to describe a more complex reality than “technology is good and/or bad?”
  • substituting computers for teachers
    • Still oriented toward the “time to task” approach. But that’s good enough for cognitive science, which tends to be favourably viewed in educational fields.
  • supplement
    • Kept thinking about the well-known Hawthorne effect. In this case, the very idea that providing students with supplementary “care” can be seen as an obvious approach which is most often discussed in the field instead of at the higher levels of decision-making.
  • The OLPC concept has been pioneered in a number of school districts in the United States over the last decade
    • From a 2005 project targeting “countries with inconsistent power grids,” we get to a relatively long series of initiatives in individual school districts in the USofA since last century. Telescoping geographical and temporal scales. And, more importantly, assigning the exact same “concept” to diverse projects.
  • Negroponte has explicitly derided
    • Not the only thing Negroponte derides. He’s been a professional derider for a while, now.
      Negroponte’s personality is part of the subtext of any OLPC-related piece. It’d be interesting to analyse him in view of the “mercurial CEO” type which fascinates a number of people.
  • It must be said
    • Acknowledging the fact that there is more to the situation than what this piece is pushing.
  • academic
    • In this context, “academic” can have a variety of connotations, many of which are relatively negative.
  • teachers limited access to the computers
    • Typically, teachers have relatively little control in terms of students’ access to computers so it sounds likely that the phrase should have read “had limited access.” But, then again, maybe teachers in Hollow’s research were in fact limiting access to computers, which would be a very interesting point to bring and discuss. In fact, part of what is missing in many of those pieces about technology and learning is what access really implies. Typically, most discussions on the subject have to do with time spent alone with such a tool, hence the “one…per child” part of the OLPC approach. But it’s hard to tell if there has been any thought about the benefits of group access to tools or limited access to such tools.
      To go even further, there’s a broad critique of the OLPC approach, left unaddressed in this piece, about the emphasis on individual ownership of tools. In the US, it’s usually not ok for neighbours to ask about using others’ lawnmowers and ladders. It’s unsurprising that pushing individual ownership would seem logical to those who design projects from the US.
  • had not been adequately trained
    • In the OLPC context, it has been made as a case for the dark side of constructionism. The OLPC project might have been a learning project, but it wasn’t a teaching one. Some explicit comments from project members were doing little to dispel the notion that constructivism isn’t about getting rid of teachers. Even documentation for the OLPC XO contained precious little which could help teachers. Teachers weren’t the target audience. Children and governments were.
  • not silver bullets
    • Acknowledging, in an oblique way, that the situation is more complex.
  • surveys of students
    • With a clear Hawthorne effect.
  • parents rolling their eyes
    • Interesting appeal to parenting experience. Even more than teachers, they’re absent from many of these projects. Not a new pattern. Literacy projects often forget parents and the implications in terms of a generation gap. But what is perhaps more striking is that parents are also invisible in coverage of many of these issues. Contrary to “our” children, children in “those poor countries over there” are “ours to care for,” through development projects, adoptions, future immigration, etc.
  • evaluation of an OLPC project in Haiti
    • Sounds more like a pilot project than like field research. But maybe it’s more insightful.
  • Repeated calls and e-mails to OLPC and Negroponte seeking comment on OLPC did not receive a response
    • Such statements are “standard procedure” for journalists. But what is striking about this one is where it’s placed in the piece. Not only is it near the end of the argumentation but it’s in a series of comments about alternative views on the OLPC project. Whether or not it was done on purpose, the effect that we get is that there are two main voices, pro and con. Those on the con side can only have arguments in the same line of thought (about the project’s cost and “efficacy,” with possible comments about management). Those on the pro side are put in a defensive position.
      In such cases, responsiveness is often key. Though Negroponte has been an effective marketer of his pet project, the fact that he explicitly refuses to respond to criticisms and critiques makes for an even more constrained offense/defense game.
  • ironic
    • Strong words, in such a context. Because it’s not the situation which is ironic. It’s a lack of action in a very specific domain.
  • the Third World
    • Interesting that the antiquated “Third World” expression comes in two contexts: the alleged target of the OLPC project (with little discussion as to what was meant by that relationship) and as the J-PAL field of expertise.
  • a leader in
    • Peacock terms or J-PAL are on the Miller-McCune lovelist?
  • There are
    • This is where the piece switches. We’re not talking about the OLPC, anymore. We reduce OLPC to a single goal, which has allegedly not been met, and propose that there are better ways to achieve this goal. Easy and efficient technique, but there still seems to be something missing.
  • etting children in developing countries into school and helping them learn more while they are there
    • A more specific goal than it might seem, at first blush.
      For a very simple example: how about homeschooling?
  • proven successful
    • “We have proof!”
  • cheap
    • One might have expected “inexpensive,” here, instead of “cheap.” But, still, the emphasis is on cost.
  • deworming
    • Sounds a little bit surprising a switch from computer tech to public health.
  • 50 cents per child per year
  • $4 per student per year
  • 30 percent increase in lifetime earnings
  • technology-based approaches to improving student learning in the developing world
    • Coming back to technology, to an extent, but almost in passing. Technology, here, can still be a saviour. The issue would be to find the key technology to solve that one problem (student learning in the developing world needs calls for improvement). Rather limited in scope, depth, insight.
  • show more promise than one laptop per child
    • Perhaps the comment most directly related to opinions. “Showing promise” is closer to “instinctive appeal” but, in this case, it’s a positive. We don’t need to apply critical thinking to something which shows promise. It’s undeniably good. Right?
  • the J-PAL co-founder
    • There we are!
  • $2.20
  • Remedial education
  • A study in Kenya
    • Reference needed.
  • it didn’t matter
    • Sounds like a bold statement, as it’s not expressly linked to the scope of the study. It probably did matter. Just not in terms of what was measured. Mattering has to do with significance in general, not just with statistical significance.
  • expensive
    • Cost/benefits are apparently the only two “factors” to consider.
  • quarter of the cost
  • cheaper
  • $2 per month
  • $3 per month

Vague expérience

Bon, ça fait déjà quelques temps que je suis sur Google Wave alors il me faudrait commencer à parler de mon expérience. J’ai pris pas mal de notes et j’ai remarqué des tas de choses. Mais vaut mieux commencer par quelques petits points…

J’écrivais une réponse à une amie sur Facebook dont les amis tentaient d’en savoir plus à propos de Wave. Et ça m’a donné l’occasion de mettre quelques idées en place.

 

Wave est un drôle de système. Comme Twitter lors des premières utilisations, c’est difficile de se faire une idée. Surtout que c’est une version très préliminaire, pleine de bogues.

Jusqu’à maintenant, voici les ressources que j’ai trouvé utiles:
http://lifehacker.com/5376138/google-wave-101
http://danieltenner.com/posts/0012-google-wave.html

(Oui, en anglais. Je traduirai pas, à moins qu’il y ait de la demande.)

Le guide suivant risque en effet d’être le plus complet. Je l’ai pas encore lu…
http://completewaveguide.com/

Sinon, version relativement courte…
Wave est un outil de communication basé sur la notion que les participants à l’événement de communication (la discussion, dions) ont accès à un contenu centralisé. Donc, plutôt que d’échanger des courriels, on construit une “wave” qui peut contenir des tas de choses. On pense surtout au texte mais le contenu est très flexible.
Quelques forces…
– On passe du temps réel au mode asynchrone. Donc, on peut commencer une conversation comme si c’était un échange de courriels puis se faire une séance de clavardage dans le même contenu et retourner au mode courriel plus tard. Très utile et exactement le genre de truc dont plusieurs ont besoin, s’ils échangent des idées à propos de contenus.
– Comme Wiki, SubEthaEdit ou même Google Docs, c’est de l’écriture collaborative. Donc, on peut facilement construire du contenu avec plusieurs autres personnes. Le système permet un suivi plus facile que sur un Wiki ou avec Google Docs.
– La gestion des accès est incroyablement facile. En ce moment, on ne peut pas retirer quelqu’un qu’on a ajouté à une “wave”, mais c’est vraiment très facile de spécifier qui on veut ajouter comme participants à une “wave” ou même à une plus petite section. Donc, on peut conserver certaines choses plus privées et d’autres presque publiques. Ça semble simple, mais c’est assez important, comme changement. On peut créer des listes ad hoc comme si on décidait soudainement de faire équipe.
– C’est une architecture ouverte, avec la possibilité de créer des outils pour transformer les contenus ou pour ajouter d’autres choses (cartes, contenus interactifs, sondages…). Du genre widgets, mais ça va plus loin. Et ça motive le monde des développeurs. L’idée, c’est que le système permet d’être étendu de façon inattendue.
– C’est si nouveau et relativement limité dans le nombre d’utilisateurs qu’on en est à une phase où tout le monde essaie d’expérimenter et accepte de répondre à toute question.

– Il n’y a pour l’instant pas de pourriel.

Bon, c’est déjà pas si court… 😉

Si vous avez des questions, faites-moi signe. Si vous êtes déjà sur Wave, je suis enkerli et informalethnographer (dans les deux cas, c’est @googlewave.com).

Cours sur le Web social

Le cours TÉLUQ sur le Web social (INF6107) créé par Sébastien Paquet, assisté de Robin Millette, de Martin Lessard et de votre humble serviteur, est maintenant en-ligne. http://benhur.teluq.uquebec.ca/SPIP/inf6107/index.php

Oui, en accès complètement ouvert. Tout le contenu. Sans restriction. Les étudiants inscrits au cours pourrons obtenir des crédits de maîtrise pour ce cours, mais tout le monde peut travailler avec ce matériel.

Ma participation à la conception était surtout sur le module 6 et sur le module 7. Ceux qui voudraient discuter le contenu de ces modules peuvent me contacter.

Je sais pas si le cours est officiellement commencé, mais il y a maintenant des gens qui en parlent sur Twitter, y compris Mario Asselin.

Canadian Barista Championship: 2009 Results

  1. Kyle Straw, Caffè Artigiano, Vancouver, BC (663 points)
  2. Anthony Benda, Café Myriade, Montreal, Qc (627 points)
  3. Chad Moss, Transcend Coffee, Edmonton, AB (610 points)
  4. Robert Kettner, Fernwood Coffee Roasting, Victoria, BC (601 points)
  5. Spencer Viehweger, JJ Bean Coffee Roasters, Vancouver, BC (592.5 points)
  6. Joel May, Fratello Coffee Roasters, Calgary, AB (576.5 points)

Barista’s Choice (Reggie Award)

Anthony Benda, Café Myriade, Montreal, Qc

Coffee at CBC

Went to @cbchomerun to talk about coffee. If you got here because of my short intervention, welcome!

Here are some of my coffee-related blogposts

http://enkerli.wordpress.com/2007/08/13/montreal-coffee-renaissance/
(thoughts on a new phase for Montreal’s coffee scene)
http://enkerli.wordpress.com/2008/11/21/cafe-a-la-montrealaise/ (Long,
in French)
http://enkerli.wordpress.com/2008/06/18/eastern-canadian-espresso/
(about the Eastern Regional Canadian Barista Championships, last year)
http://enkerli.wordpress.com/2008/10/27/first-myriade-session/ (when
Myriade opened)
http://enkerli.wordpress.com/2008/10/27/more-notes-on-myriade/
http://enkerli.wordpress.com/2008/11/18/cafe-myriade-linkfest/
http://enkerli.wordpress.com/2006/02/16/glocal-craftiness-coffee-beer-music/
(musings on global/local issues about coffee, beer, music)
http://enkerli.wordpress.com/2006/03/04/caffe-artjava-real-espresso-in-montreal/
(when the Third Wave first came to Mtl)
http://enkerli.wordpress.com/2009/08/25/beer-eye-for-the-coffee-guy-or-gal/
(musings on coffee-focused communities)

Also, my “mega-thread” on CoffeeGeek about Brikka and other stovetop moka pots (in my mind, ideal for homemade coffee):

http://www.coffeegeek.com/forums/coffee/machines/220503

Feel free to contact me if you want to talk coffee, espresso, cafés, geekness…

What's So "Social" About "Social Media?" (Podcamp Montreal Topic)

It’s all good and well to label things “social media” but those of us who are social scientists need to speak up about some of the insight we can share.
If social scientists and social media peeps make no effort at talking with one another, social media will suffer and social scientists will be shut out of something important.
Actually, social media might provide one of the most useful vantage points to look at diverse social issues, these days. And participants social media could really benefit from some basic social analysis.
Let’s talk about this.

Will be participating in this year’s Podcamp Montreal. Last year’s event had a rather big impact on me. (It’s at #pcmtl08 that I “came out of the closet” as a geek!) At that time, I presented on “Social Acamedia” (Slides, Audio). Been meaning to do a slidecast but never got a round tuit.

My purpose, this year, is in a way to follow up on this blogpost of mine (from the same period) about “The Need for Social Science in Social Web/Marketing/Media.”

As it’s a BarCamp-style unconference, I’ll do this in a very casual way. I might actually not use slides or anything like that. And I guess I could use my time for a discussion, more than anything else. I’ll be missing much of the event because I’m teaching on Saturday. So my session comes in a very different context from last year’s, when I was able to participate in all sorts of things surrounding #pcmtl.

Yup. Come to think of it, a conversation makes more sense, as I’ll be getting condensed insight from what happens before. I still might start with a 15 minute spiel, but I really should spend as much time as possible just discussing these issues with people. Isabelle Lopez did a workshop-style session last year and that was quite useful.

The context for this year’s session is quite specific. I’ve been reorienting myself as an “informal ethnographer.” I eventually started my own podcast on ethnography, I’ve been doing presentations and workshops both on social media and on social analysis of online stuff, I was even able to participate in the creation of material for a graduate course about the “Social Web”…

Should be fun.

War of the Bugs: Playing with Life in the Brewery

Kept brewing and thinking about brewing, after that last post. Been meaning to discuss my approach to “brewing bugs”: the yeast and bacteria strains which are involved in some of my beers. So, it’s a kind of follow-up.

Perhaps more than a reason for me to brew, getting to have fun with these living organisms is something of an achievement. It took a while before it started paying off, but it now does.

Now, I’m no biochemist. In fact, I’m fairly far to “wet sciences” in general. What I do with these organisms is based on a very limited understanding of what goes on during fermentation. But as long as I’m having fun, that should be ok.

This blogpost is about yeast in brewing. My focus is on homebrewing but many things also apply to craft brewing or even to macrobreweries.

There’s supposed to be a saying that “brewers make wort, yeast makes beer.” Whether or not it’s an actual saying, it’s quite accurate.

“Wort” is unfermented beer. It’s a liquid containing fermentable sugars and all sorts of other compounds which will make their way into the final beer after the yeast has had its fun in it. It’s a sweet liquid which tastes pretty much like Malta (e.g. Vitamalt).

Yeast is a single-cell organism which can do a number of neat things including the fine act of converting simple sugars into alcohol and CO2. Yeast cells also do a number of other neat (and not so neat) things with the wort, including the creation of a large array of flavour compounds which can radically change the character of the beer. Among the four main ingredients in beer (water, grain, hops, and yeast), I’d say that yeast often makes the largest contribution to the finished beer’s flavour and aroma profile.

The importance of yeast in brewing has been acknowledged to different degrees in history. The well-known Reinheitsgebot “purity law” of 1516, which specifies permissible ingredients in beer, made no mention of yeast. As the story goes, it took Pasteur (and probably others) to discover the role of yeast in brewing. After this “discovery,” Pasteur and others have been active at isolating diverse yeast strains to be used in brewing. Before that time, it seems that yeast was just occurring naturally in the brewing process.

As may be apparent in my tone, I’m somewhat skeptical of the “discovery” narrative. Yeast may not have been understood very clearly before Pasteur came on the scene, but there’s some evidence showing that yeast’s contribution to brewing had been known in different places at previous points in history. It also seems likely that multiple people had the same basic insight as LP did but may not have had the evidence to support this insight. This narrative is part of the (home)brewing “shared knowledge.”

But I’m getting ahead of myself.

There’s a lot to be said about yeast biochemistry. In fact, the most casual of brewers who spends any significant amount of time with online brewing resources has some understanding, albeit fragmentary, of diverse dimensions of biochemistry through the action of yeast. But this blogpost isn’t about yeast biochemistry.

I’m no expert and biochemistry is a field for experts. What tends to interest me more than the hard science on yeast is the kind of “folk science” brewers create around yeast. Even the most scientific of brewers occasionally talks about yeast in a way which sounds more like folk beliefs than like hard science. In ethnographic disciplines, there’s a field of “ethnoscience” which deals with this kind of “folk knowledge.” My characterization of “folk yeast science” will probably sound overly simplistic and I’m not saying that it accurately represents a common approach to yeast among brewers. It’s more in line with the tone of Horace Miner’s classic text about the Nacirema than with anything else. A caricature, maybe, but one which can provide some insight.

In this case, because it’s a post on my personal blog, it probably provides more insight about yours truly than about anybody else. So be it.

I’m probably more naïve than most. Or, at least, I try to maintain a sense of wonder, as I play with yeast. I’ve done just enough reading about biochemistry to be dangerous. Again, “the brewery is an adult’s chemistry set.”

A broad distinction in the brewer’s approach to yeast is between “pure” and “wild” yeast. Pure yeast usually comes to the brewer from a manufacturer but it originated in a well-known brewery. Wild yeast comes from the environment and should be avoided at all costs. Wild yeast infects and spoils the wort. Pure yeast is a brewer’s best friend as it’s the one which transforms sweet wort into tasty, alcoholic beer. Brewers do everything to “keep the yeast happy.” Though yeast happiness sounds like exaggeration on my part, this kind of anthropomorphic concept is clearly visible in discussions among brewers. (Certainly, “yeast health” is a common concept. It’s not anthropomorphic by itself, but it takes part in the brewer’s approach to yeast as life.) Wild yeast is the reason brewers use sanitizing agents. Pure yeast is carefully handled, preserved, “cultured.” In this context, “wild yeast” is unwanted yeast. “Pure yeast” is the desirable portion of microflora.

It wouldn’t be too much of an exaggeration to say that many brewers are obsessed with the careful handling of pure yeast and the complete avoidance of wild yeast. The homebrewer’s motto, following Charlie Papazian, may be “Relax, Don’t Worry, Have a Homebrew,” when brewers do worry, they often worry about keeping their yeast as pure as possible or keeping their wort as devoid of wild yeast as possible.

In the context of brewers’ folk taxonomy, wild yeast is functionally a “pest,” its impact is largely seen as negative. Pure yeast is beneficial. Terms like “bugs” or “beasties” are applied to both but, with wild yeast, their connotations and associations are negative (“nasty bugs”) while the terms are applied to pure yeast in a more playful, almost endeared tone. “Yeasties” is almost a pet name for pure yeast.

I’ve mentioned “folk taxonomy.” Here, I’m mostly thinking about cognitive anthropology. Taxonomies have been the hallmark of cognitive anthropology, as they reveal a lot about the ways people conceive of diverse parts of reality and are relatively easy to study. Eliciting categories in a folk taxonomy is a relatively simple exercise which can even lead to other interesting things in terms of ethnographic research (including, for instance, establishing rapport with local experts or providing a useful basis to understanding subtleties in the local language). I use terms like “folk” and “local” in a rather vague way. The distinction is often with “Western” or even “scientific.” Given the fact that brewing in North America has some strong underpinnings in science, it’s quite fun to think about North American homebrewers through a model which involves an opposition to “Western/scientific.” Brewers, including a large proportion of homebrewers, tend to be almost stereotypically Western and to work through (and sometimes labour under) an almost-reductionist scientific mindframe. In other words, my talking about “folk taxonomy” is almost a way to tease brewers. But it also relates to my academic interest in cultural diversity, language, worldviews, and humanism.

“Folk taxonomies” can be somewhat fluid but the concept applies mostly to classification systems which are tree-like, with “branches” coming of broader categories. The term “folksonomy” has some currency, these days, to refer to a classification structure which has some relation to folk taxonomy but which doesn’t tend to work through a very clear arborescence. In many contexts, “folksonomy” simply means “tagging,” with the notion that it’s a free-form classification, not amenable to treatment in the usual “hierarchical database” format. Examples of folksonomies often have to do with the way people classify books or other sources of information. A folksonomy is then the opposite of the classification system used in libraries or in Web directories such as the original Yahoo! site. Tags assigned to this blogpost (“Tagged: Belgian artist…”) are part of my own folksonomy for blogposts. Categories on WordPress blogs such as this ones are supposed to create more of a (folk) taxonomy. For several reasons (including the fact that tags weren’t originally available to me for this blog), I tend to use categories as more of a folksonomy, but with a bit more structure. Categories are more stable than tags. For a while, now, I’ve refrained from adding new categories (to my already overly-long list). But I do add lots of new tags.

Anyhoo…

Going back to brewers’ folk taxonomy of yeast strains…

Technically, if I’m not mistaken, the term “pure” should probably refer to the yeast culture, not to the yeast itself. But the overall concept does seem to apply to types of yeast, even if other terms are used. The terms “wild” and “pure” aren’t inappropriate. “Wild” yeast is undomesticated. “Pure” yeast strains were those strains which were selected from wild yeast strains and were isolated in laboratories.

Typically, pure yeast strains come from one of two species of the genus Saccharomyces. One species includes the “top-fermenting” yeast strains used in ales while the other species includes the “bottom-fermenting” yeast strains used in lagers. The distinction between ale and lager is relatively recent, in terms of brewing history, but it’s one which is well-known among brewers. The “ale” species is called cerevisiae (with all sorts of common misspellings) and the “lager” species has been called different names through history, to the extent that the most appropriate name (pastorianus) seems to be the object of specialized, not of common knowledge.

“Wild yeast” can be any yeast strain. In fact, the two species of pure yeast used in brewing exist as wild yeast and brewers’ “folk classification” of microorganisms often lumps bacteria in the “wild yeast” category. The distinction between bacteria and yeast appears relatively unimportant in relation to brewing.

As can be expected from my emphasis on “typically,” above, not all pure yeast strains belong to the “ale” and “lager” species. And as is often the case in research, the exceptions are where things get interesting.

One category of yeast which is indeed pure but which doesn’t belong to one of the two species is wine yeast. While brewers do occasionally use strains of wild yeast when making other beverages besides beer, wine yeast strains mostly don’t appear on the beer brewer’s radar as being important or interesting. Unlike wild yeast, it shouldn’t be avoided at all costs. Unlike pure yeast, it shouldn’t be cherished. In this sense, it could almost serve as «degré zéro» or “null” in the brewer’s yeast taxonomy.

Then, there are yeast strains which are usually considered in a negative way but which are treated as pure strains. I’m mostly thinking about two of the main species in the Brettanomyces genus, commonly referred to as “Brett.” These are winemakers’ pests, especially in the case of oak aging. Oak casks are expensive and they can be ruined by Brett infections. In beer, while Brett strains are usually classified as wild yeast, some breweries have been using Brett in fermentation to effects which are considered by some people to be rather positive while others find these flavours and aromas quite displeasing. It’s part of the brewing discourse to use “barnyard” and “horse blanket” as descriptors for some of the aroma and flavour characteristics given by Brett.

Brewers who consciously involve Brett in the fermentation process are rather uncommon. There are a few breweries in Belgium which make use of Brett, mostly in lambic beers which are fermented “spontaneously” (without the use of controlled innoculation). And there’s a (slightly) growing trend among North American home- and craft brewers toward using Brett and other bugs in brewing.

Because of these North American brewers, Brett strains are now available commercially, as “pure” strains.

Which makes for something quite interesting. Brett is now part of the “pure yeast” category, at least for some brewers. They then use Brett as they would other pure strains, taking precautions to make sure it’s not contaminated. At the same time, Brett is often used in conjunction with other yeast strains and, contrary to the large majority of beer fermentation methods, what brewers use is a complex yeast culture which includes both Saccharomyces and Brett. It may not seem that significant but it brings fermentation out of the strict “mono-yeast” model. Talking about “miscegenation” in social terms would be abusive. But it’s interesting to notice which brewers use Brett in this way. In some sense, it’s an attitude which has dimensions from both the “Belgian Artist” and “German Engineer” poles in my brewing attitude continuum.

Other brewers use Brett in a more carefree way. Since Brett-brewing is based on a complex culture, one can go all the way and mix other bugs. Because Brett has been mostly associated with lambic brewing, since the onset of “pure yeast” brewing, the complex cultures used in lambic breweries serve as the main model. In those breweries, little control can be applied to the balance between yeast strains and the concept of “pure yeast” seems quite foreign. I’ve never visited a lambic brewery (worse yet, I’ve yet to set foot in Belgium), but I get to hear and read a lot about lambic brewing. My perception might be inaccurate, but it also reflects “common knowledge” among North American brewers.

As you might guess, by now, I take part in the trend to brew carefreely. Even carelessly. Which makes me more of a MadMan than the majority of brewers.

Among both winemakers and beer brewers, Brett has the reputation to be “resilient.” Once Brett takes hold of your winery or brewery, it’s hard to get rid of it. Common knowledge about Brett includes different things about its behaviour in the fermentation process (it eats some sugars that Saccharomyces doesn’t, it takes a while to do its work…). But Brett also has a kind of “character,” in an almost-psychological sense.

Which reminds me of a comment by a pro brewer about a well-known strain of lager yeast being “wimpy,” especially in comparison with some well-known British ale yeast strains such as Ringwood. To do their work properly, lager strains tend to require more care than ale strains, for several reasons. Ringwood and some other strains are fast fermenters and tend to “take over,” leaving little room for other bugs.

Come to think of it, I should try brewing with a blend of Ringwood and Brett. It’d be interesting to see “who wins.”

Which brings me to “war.”

Now, I’m as much of a pacifist as one can be. Not only do I not tend to be bellicose and do I cherish peace, I frequently try to avoid conflict and I even believe that there’s a peaceful resolution to most situations.

Yet, one thing I enjoy about brewing is to play with conflicting yeast strains. Pitting one strain against another is my way to “wage wars.” And it’s not very violent.

I also tend to enjoy some games which involve a bit of conflict, including Diplomacy and Civilization. But I tend to play these games as peacefully as possible. Even Spymaster, which rapidly became focused on aggressions, I’ve been playing as a peace-loving, happy-go-lucky character.

But, in the brewery, I kinda like the fact that yeast cells from different strains are “fighting” one another. I don’t picture yeast cells like warriors (with tiny helmets), but I do have fun imagining the “Battle of the Yeast.”

Of course, this has more to do with competition than with conflict. But both are related, in my mind. I’m also not that much into competition and I don’t like to pit people against one another, even in friendly competition. But this is darwinian competition. True “survival of the fittest,” with everything which is implied in terms of being contextually appropriate.

So I’m playing with life, in my brewery. I’m not acting as a Creator over the yeast population, but there’s something about letting yeast cells “having at it” while exercising some level of control that could be compared to some spiritual figures.

Thinking about this also makes me think about the Life game. There are some similarities between what goes on in my wort and what Conway’s game implies. But there are also several differences, including the type of control which can be applied in either case and the fact that the interaction between yeast cells is difficult to visualize. Not to mention that yeast cells are actual, living organisms while the cellular automaton is pure simulation.

The fun I have playing with yeast cells is part of the reason I like to use Brett in my beers. The main reason, though, is that I like the taste of Brett in beer. In fact, I even like it in wine, by transfer from my taste for Brett in beer.

And then, there’s carefree brewing.

As I described above, brewers are very careful to avoid wild yeast and other unwanted bugs in their beers. Sanitizing agents are an important part of the brewer’s arsenal. Which goes well with the “German engineer” dimension of brewing. There’s an extreme position in brewing, even in homebrewing. The “full-sanitization brewery.” Apart from pure yeast, nothing should live in the wort. Actually, nothing else should live in the brewery. If it weren’t for the need to use yeast in the fermentation process, brewing could be done in a completely sterile environment. The reference for this type of brewery is the “wet science” lab. As much as possible, wort shouldn’t come in contact with air (oxidization is another reason behind this; the obsession with bugs and the distaste for oxidization often go together). It’s all about control.

There’s an obvious reason behind this. Wort is exactly the kind of thing wild yeast and other bugs really like. Apparently, slants used to culture microorganisms in labs may contain a malt-based gelatin which is fairly similar to wort. I don’t think it contains hops, but hops are an agent of preservation and could have a positive effect in such a slant.

I keep talking about “wild yeast and other bugs” and I mentioned that, in the brewer’s folk taxonomy, bacteria are equivalent to wild yeast. The distinction between yeast and bacteria matters much less in the brewery than in relation to life sciences. In the conceptual system behind brewing, bacteria is functionally equivalent to wild yeast.

Fear of bacteria and microbes is widespread, in North America. Obviously, there are many excellent medical reasons to fear a number of microorganisms. Bacteria can in fact be deadly, in the right context. Not that the mere presence of bacteria is directly linked with human death. But there’s a clear association, in a number of North American minds, between bacteria and disease.

As a North American, despite my European background, I tended to perceive bacteria in a very negative way. Even today, I react “viscerally” at the mention of bacteria. Though I know that bacteria may in fact be beneficial to human health and that the human body contains a large number of bacterial cells, I have this kind of ingrained fear of bacteria. I love cheese and yogurt, including those which are made with very complex bacterial culture. But even the mere mention of bacteria in this context requires that I think about the distinction between beneficial and dangerous bacteria. In other words, I can admit that I have an irrational fear of bacteria. I can go beyond it, but my conception of microflora is skewed.

For two years in Indiana, I was living with a doctoral student in biochemistry. Though we haven’t spent that much time talking about microorganisms, I was probably influenced by his attitude toward sanitization. What’s funny, though, is that our house wasn’t among the cleanest in which I’ve lived. In terms of “sanitary conditions,” I’ve had much better and a bit worse. (I’ve lived in a house where we received an eviction notice from the county based on safety hazards in that place. Lots of problems with flooding, mould, etc.)

Like most other North American brewers, I used to obsess about sanitization, at every step in the process. I was doing an average job at sanitization and didn’t seem to get any obvious infection. I did get “gushers” (beers which gush out of the bottle when I open it) and a few “bottle bombs” (beer bottles which actually explode). But there were other explanations behind those occurrences than contamination.

The practise of sanitizing everything in the brewery had some significance in other parts of my life. For instance, I tend to think about dishes and dishwashing in a way which has more to do with caution over potential contamination than with dishes appearing clean and/or shiny. I also think about what should be put in the refrigerator and what can be left out, based on my limited understanding of biochemistry. And I think about food safety in a specific way.

In the brewery, however, I moved more and more toward another approach to microflora. Again, a more carefree approach to brewing. And I’m getting results that I enjoy while having a lot of fun. This approach is also based on my pseudo-biochemistry.

One thing is that, in brewing, we usually boil the wort for an hour or more before inoculation with pure yeast. As boiling kills most bugs, there’s something to be said about sanitization being mostly need for equipment which touches the wort after the boil. Part of the equipment is sanitized during the boiling process and what bugs other pieces of equipment may transfer to the wort before boiling are unlikely to have negative effects on the finished beer. With this idea in mind, I became increasingly careless with some pieces of my brewing equipment. Starting with the immersion chiller and kettle, going all the way to the mashtun.

Then, there’s the fact that I use wild yeast in some fermentations. In both brewing and baking, actually. Though my results with completely “wild” fermentations have been mixed to unsatisfactory, some of my results with “partially-wild” fermentations have been quite good.

Common knowledge among brewers is that “no known pathogen can survive in beer.” From a food safety standpoint, beer is “safe” for four main reasons: boiling, alcohol, low pH, and hops. At least, that’s what is shared among brewers, with narratives about diverse historical figures who saved whole populations through beer, making water sanitary. Depending on people’s attitudes toward alcohol, these stories about beer may have different connotations. But it does seem historically accurate to say that beer played an important part in making water drinkable.

So, even wild fermentation is considered safe. People may still get anxious but, apart from off-flavours, the notion is that contaminated beer can do no more harm than other beers.

The most harmful products of fermentation about which brewers may talk are fusel alcohols. These, brewers say, may cause headaches if you get too much of them. Fusels can cause some unwanted consequences, but they’re not living organisms and won’t spread as a disease. In brewer common knowledge, “fusels” mostly have to do with beers with high degrees of alcohol which have been fermented at a high temperature. My personal sense is that fusels aren’t more likely to occur in wild fermentation than with pure fermentation, especially given the fact that most wild fermentation happens with beer with a low degree of alcohol.

Most of the “risks” associated with wild fermentation have to do with flavours and aromas which may be displeasing. Many of these have to do with souring, as some bugs transform different compounds (alcohol especially, if I’m not mistaken) into different types of acids. While Brett and other strains of wild yeast can cause some souring, the acids in questions mostly have to do with bacteria. For instance, lactobacillus creates lactic acid, acetobacter creates acetic acid, etc.

Not only do I like that flavour and aroma characteristics associated with some wild yeast strains (Brett, especially), I also like sour beers. It may sound strange given the fact that I suffer from GERD. But I don’t overindulge in sour beers. I rarely drink large quantities of beer and sour beers would be the last thing I’d drink large quantities of. Besides, there’s a lot to be said about balance in pH. I may be off but I get the impression that there are times in which sour things are either beneficial to me or at least harmless. Part of brewer common knowledge in fact has a whole thing about alkalinity and pH. I’m not exactly clear on how it affects my body based on ingestion of diverse substances, but I’m probably affected by my background as a homebrewer.

Despite my taste for sour beers, I don’t necessarily have the same reaction to all souring agents. For instance, I have a fairly clear threshold in terms of acetic acid in beer. I enjoy it when a sour beer has some acetic character. But I prefer to limit the “aceticness” of my beers. Two batches I’ve fermented with wild bugs were way too acetic for me and I’m now concerned that other beers may develop the same character. In fact, if there’s a way to prevent acetobacter from getting in my wort while still getting the other bugs working, I could be even more carefree as a brewer than I currently am.

Which is a fair deal. These days, I really am brewing carefreely. Partly because of my “discovery” of lactobacillus.

As brewer common knowledge has it, lactobacillus is just about everywhere. It’s certainly found on grain and it’s present in human saliva. It’s involved in some dairy fermentation and it’s probably the main source of bacterial fear among dairy farmers.

Apart from lambic beers (which all come from a specific region in Belgium), the main sour beer that is part of brewer knowledge is Berliner Weisse. Though I have little data on how Berliner Weisse is fermented, I’ve known for a while that some people create a beer akin to Berliner Weisse through what brewers call a “sour mash” (and which may or may not be related to sour mash in American whiskey production). After thinking about it for years, I’ve done my first sour mash last year. I wasn’t very careful in doing it but I got satisfying results. One advantage of the sour mash is that it happens before boiling, which means that the production of acid can be controlled, to a certain degree. While I did boil my wort coming from sour mash, it’s clear that I still had some lactobacillus in my fermenters. It’s possible that my boil (which was much shorter than the usual) wasn’t enough to kill all the bugs. But, come to think of it, I may have been a bit careless with sanitization of some pieces of equipment which had touched the sour wort before boiling. Whatever the cause, I ended up with some souring bugs in my fermentation. And these worked really well for what I wanted. So much so that I’ve consciously reused that culture in some of my most recent brewing experiments.

So, in my case, lactobacillus is in the “desirable” category of yeast taxonomy. With Brett and diverse Saccharomyces strains, lactobacillus is part of my fermentation apparatus.

As a mad brewer, I can use what I want to use. I may not create life, but I create beer out of this increasingly complex microflora which has been taking over my brewery.

And I’m a happy brewer.

How I Got Into Beer

Was doing some homebrewing experimentation (sour mash, watermelon, honey, complex yeast cultures…) and I got to think about what I’d say in an interview about my brewing activities.

It’s a bit more personal than my usual posts in English (my more personal blogposts are usually in French), but it seems fitting.

I also have something of a backlog of blogposts I really should do ASAP. But blogging is also about seizing the moment. I feel like writing about beer. 😛

So…

As you might know, the drinking age in Quebec is 18, as in most parts of the World except for the US. What is somewhat distinct about Qc with regards to drinking age is that responsible drinking is the key and we tend to have a more “European” attitude toward alcohol: as compared to the Rest of Canada, there’s a fair bit of leeway in terms of when someone is allowed to drink alcohol. We also tend to learn to drink in the family environment, and not necessarily with friends. What it means, I would argue, is that we do our mistakes in a relatively safe context. By the time drinking with peers becomes important (e.g., in university or with colleagues), many of us know that there’s no fun in abusing alcohol and that there are better ways to prove ourselves than binge drinking. According to Barrett Seaman, author of Binge: What Your College Student Won’t Tell You, even students from the US studying at McGill University in Montreal are more likely to drink responsibly than most students he’s seen in the US. (In Montreal, McGill tends to be recognized as a place where binge drinking is most likely to occur, partly because of the presence of US students. In addition, binge drinking is becoming more conspicuous, in Qc, perhaps because of media pressure or because of influence from the US.)

All this to say that it’s rather common for a Québécois teen to at least try alcohol at a relatively age. Because of my family’s connections with Switzerland and France, we probably pushed this even further than most Québécois family. In other words, I had my first sips of alcohol at a relatively early age (I won’t tell) and, by age 16, I could distinguish different varieties of Swiss wines, during an extended trip to Switzerland. Several of these wines were produced by relatives and friends, from their own vineyards. They didn’t contain sulfites and were often quite distinctive. To this day, I miss those wines. In fact, I’d say that Swiss wines are among the best kept secrets of the wine world. Thing is, it seems that Swiss vineyards barely produce enough for local consumption so they don’t try to export any of it.

Anyhoo…

By age 18, my attitude toward alcohol was already quite similar to what it is now: it’s something that shouldn’t be abused but that can be very tasty. I had a similar attitude toward coffee, that I started to drink regularly when I was 15. (Apart from being a homebrewer and a beer geek, I’m also a homeroaster and coffee geek. Someone once called me a “Renaissance drinker.”)

When I started working in French restaurants, it was relatively normal for staff members to drink alcohol at the end of the shift. In fact, at one place where I worked, the staff meal at the end of the evening shift was a lengthy dinner accompanied by some quality wine. My palate was still relatively untrained, but I remember that we would, in fact, discuss the wine on at least some occasions. And I remember one customer, a stage director, who would share his bottle of wine with the staff during his meal: his doctor told him to reduce his alcohol consumption and the wine only came in 750ml bottles. 😉

That same restaurant might have been the first place where I tried a North American craft beer. At least, this is where I started to know about craft beer in North America. It was probably McAuslan‘s St. Ambroise Stout. But I also had opportunities to have some St. Ambroise Pale Ale. I just preferred the Stout.

At one point, that restaurant got promotional beer from a microbrewery called Massawippi. That beer was so unpopular that we weren’t able to give it away to customers. Can’t recall how it tasted but nobody enjoyed it. The reason this brewery is significant is that their license was the one which was bought to create a little microbrewery called Unibroue. So, it seems that my memories go back to some relatively early phases in Quebec’s craft beer history. I also have rather positive memories of when Brasal opened.

Somewhere along the way, I had started to pick up on some European beers. Apart from macros (Guinness, Heineken, etc.), I’m not really sure what I had tried by that point. But even though these were relatively uninspiring beers, they somehow got me to understand that there was more to beer than Molson, Labatt, Laurentide, O’Keefe, and Black Label.

The time I spent living in Switzerland, in 1994-1995, is probably the turning point for me in terms of beer tasting. Not only did I get to drink the occasional EuroLager and generic stout, but I was getting into Belgian Ales and Lambics. My “session beer,” for a while, was a wit sold in CH as Wittekop. Maybe not the most unique wit out there. But it was the house beer at Bleu Lézard, and I drank enough of it then to miss it. I also got to try several of the Trappists. In fact, one of the pubs on the EPFL campus had a pretty good beer selection, including Rochefort, Chimay, Westmalle, and Orval. The first lambic I remember was Mort Subite Gueuze, on tap at a very quirky place that remains on my mind as this near-cinematic experience.

At the end of my time in Switzerland, I took a trip to Prague and Vienna. Already at that time, I was interested enough in beer that a significant proportion of my efforts were about tasting different beers while I was there. I still remember a very tasty “Dopplemalz” beer from Vienna and, though I already preferred ales, several nice lagers from Prague.

A year after coming back to North America, I traveled to Scotland and England with a bunch of friends. Beer was an important part of the trip. Though I had no notion of what CAMRA was, I remember having some real ales in diverse places. Even some of the macro beers were different enough to merit our interest. For instance, we tried Fraoch then, probably before it became available in North America. We also visited a few distilleries which, though I didn’t know it at the time, were my first introduction to some beer brewing concepts.

Which brings me to homebrewing.

The first time I had homebrew was probably at my saxophone teacher’s place. He did a party for all of us and had brewed two batches. One was either a stout or a porter and the other one was probably some kind of blonde ale. What I remember of those beers is very vague (that was probably 19 years ago), but I know I enjoyed the stout and was impressed by the low price-quality ratio. From that point on, I knew I wanted to brew. Not really to cut costs (I wasn’t drinking much, anyway). But to try different beers. Or, at least, to easily get access to those beers which were more interesting than the macrobrewed ones.

I remember another occasion with a homebrewer, a few years later. I only tried a few sips of the beer but I remember that he was talking about the low price. Again, what made an impression on me wasn’t so much the price itself. But the low price for the quality.

At the same time, I had been thinking about all sorts of things which would later become my “hobbies.” I had never had hobbies in my life but I was thinking about homeroasting coffee, as a way to get really fresh coffee and explore diverse flavours. Thing is, I was already this hedonist I keep claiming I am. Tasting diverse things was already an important pleasure in my life.

So, homebrewing was on my mind because of the quality-price ratio and because it could allow me to explore diverse flavours.

When I moved to Bloomington, IN, I got to interact with some homebrewers. More specifically, I went to an amazing party thrown by an ethnomusicologist/homebrewer. The guy’s beer was really quite good. And it came from a full kegging system.

I started dreaming.

Brewpubs, beerpubs, and microbreweries were already part of my life. For instance, without being a true regular, I had been going to Cheval blanc on a number of occasions. And my “go to” beer had been Unibroue, for a while.

At the time, I was moving back and forth between Quebec and Indiana. In Bloomington, I was enjoying beers from Upland’s Brewing Co., which had just opened, and Bloomington Brewing Co., which was distributed around the city. I was also into some other beers, including some macro imports like Newcastle Brown Ale. And, at liquor stores around the city (including Big Red), I was discovering a few American craft beers, though I didn’t know enough to really make my way through those. In fact, I remember asking for Unibroue to be distributed there, which eventually happened. And I’m pretty sure I didn’t try Three Floyds, at the time.

So I was giving craft beer some thought.

Then, in February 1999, I discovered Dieu du ciel. I may have gone there in late 1998, but the significant point was in February 1999. This is when I tried their first batch of “Spring Equinox” Maple Scotch Ale. This is the beer that turned me into a homebrewer. This is the beer that made me changed my perspetive about beer. At that point, I knew that I would eventually have to brew.

Which happened in July 1999, I think. My then-girlfriend had offered me a homebrewing starter kit as a birthday gift. (Or maybe she gave it to me for Christmas… But I think it was summer.) Can’t remember the extent to which I was talking about beer, at that point, but it was probably a fair bit, i.e., I was probably becoming annoying about it. And before getting the kit, I was probably daydreaming about brewing.

Even before getting the kit, I had started doing some reading. The aforementioned ethnomusicologist/homebrewer had sent me a Word file with a set of instructions and some information about equipment. It was actually much more elaborate than the starter kit I eventually got. So I kept wondering about all the issues and started getting some other pieces of equipment. In other words, I was already deep into it.

In fact, when I got my first brewing book, I also started reading feverishly, in a way I hadn’t done in years. Even before brewing the first batch, I was passionate about brewing.

Thanks to the ‘Net, I was rapidly amassing a lot of information about brewing. Including some recipes.

Unsurprisingly, the first beer I brewed was a maple beer, based on my memory of that Dieu du ciel beer. However, for some reason, that first beer was a maple porter, instead of a maple scotch ale. I brewed it with extract and steeped grain. I probably used a fresh pack of Coopers yeast. I don’t think I used fresh hops (the beer wasn’t supposed to be hop-forward). I do know I used maple syrup at the end of boil and maple sugar at priming.

It wasn’t an amazing beer, perhaps. But it was tasty enough. And it got me started. I did a few batches with extract and moved to all-grain almost right away. I remember some comments on my first maple porter, coming from some much more advanced brewers than I was. They couldn’t believe that it was an extract beer. I wasn’t evaluating my extract beer very highly. But I wasn’t ashamed of it either.

Those comments came from brewers who were hanging out on the Biéropholie website. After learning about brewing on my own, I had eventually found the site and had started interacting with some local Québécois homebrewers.

This was my first contact with “craft beer culture.” I had been in touch with fellow craft beer enthusiasts. But hanging out with Bièropholie people and going to social events they had organized was my first foray into something more of a social group with its associated “mode of operation.” It was a fascinating experience. As an ethnographer and social butterfly, this introduction to the social and cultural aspects of homebrewing was decisive. Because I was moving all the time, it was hard for me to stay connected with that group. But I made some ties there and I still bump into a few of the people I met through Bièropholie.

At the time I first started interacting with the Bièropholie gang, I was looking for a brewclub. Many online resources mentioned clubs and associations and they sounded exactly like the kind of thing I needed. Not only for practical reasons (it’s easier to learn techniques in such a context, getting feedback from knowledgeable people is essential, and tasting other people’s beers is an eye-opener), but also for social reasons. Homebrewing was never meant to be a solitary experience, for me.

I was too much of a social butterfly.

Which brings me back to childhood. As a kid, I was often ostracized. And I always tried to build clubs. It never really worked. Things got much better for me after age 15, and I had a rich social life by the time I became a young adult. But, in 2000-2001, I was still looking for a club to which I could belong. Unlike Groucho, I cared a lot about any club which would accept me.

As fun as it was, Bièropholie wasn’t an actual brewclub. Brewers posting on the site mostly met as a group during an annual event, a BBQ which became known as «Xè de mille» (“Nth of 1000”) in 2001. The 2000 edition (“0th of 1000”) was when I had my maple porter tasted by more advanced brewers. Part of event was a bit like what brewclub meetings tend to be: tasting each other’s brews, providing feedback, discussing methods and ingredients, etc. But because people didn’t meet regularly as a group, because people were scattered all around Quebec, and because there wasn’t much in terms of “contribution to primary identity,” it didn’t feel like a brewclub, at least not of the type I was reading about.

The MontreAlers brewclub was formed at about that time. For some reason, it took me a while to learn of its existence. I distinctly remember looking for a Montreal-based club through diverse online resources, including the famed HomeBrew Digest. And I know I tried to contact someone from McGill who apparently had a club going. But I never found the ‘Alers.

I did eventually find the Members of Barleyment. Or, at least, some of the people who belonged to this “virtual brewclub.” It probably wasn’t until I moved to New Brunswick in 2003, but it was another turning point. One MoB member I met was Daniel Chisholm, a homebrewer near Fredericton, NB, who gave me insight on the New Brunswick beer scene (I was teaching in Fredericton at the time). Perhaps more importantly, Daniel also invited me to the Big Strange New Brunswick Brew (BSNBB), a brewing event like the ones I kept dreaming about. This was partly a Big Brew, an occasion for brewers to brew together at the same place. But it was also a very fun social event.

It’s through the BSNBB that I met MontreAlers Andrew Ludwig and John Misrahi. John is the instigator of the MontreAlers brewclub. Coming back to Montreal a few weeks after BSNBB, I was looking forward to attend my first meeting of the ‘Alers brewclub, in July 2003.

Which was another fascinating experience. Through it, I was able to observe different attitudes toward brewing. Misrahi, for instance, is a fellow experimental homebrewer to the point that I took to call him “MadMan Misrahi.” But a majority of ‘Alers are more directly on the “engineering” side of brewing. I also got to observe some interesting social dynamics among brewers, something which remained important as I moved to different places and got to observe other brewclubs and brewers meetings, such as the Chicago Beer Society’s Thirst Fursdays. Eventually, this all formed the backdrop for a set of informal observations which were the corse of a presentation I gave about craft beer and cultural identity.

Through all of these brewing-related groups, I’ve been positioning myself as an experimenter.  My goal isn’t necessarily to consistently make quality beer, to emulate some beers I know, or to win prizes in style-based brewing competitions. My thing is to have fun and try new things. Consistent beer is available anywhere and I drink little enough that I can afford enough of it. But homebrewing is almost a way for me to connect with my childhood.

There can be a “mad scientist” effect to homebrewing. Michael Tonsmeire calls himself The Mad Fermentationist and James Spencer at Basic Brewing has been interviewing a number of homebrewer who do rather unusual experiments.

I count myself among the ranks of the “Mad Brewers.” Oh, we’re not doing anything completely crazy. But slightly mad we are.

Through the selective memory of an adult with regards to his childhood, I might say that I was “always like that.” As a kid, I wanted to be everything at once: mayor, astronaut, fireman, and scholar. The researcher’s spirit had me “always try new things.” I even had a slight illusion of grandeur in that I would picture myself accomplishing all sorts of strange things. Had I known about it as a kid, I would have believed that I could solve the Poincaré conjecture. Mathematicians were strange enough for me.

But there’s something more closely related to homebrewing which comes back to my mind as I do experiments with beer. I had this tendency to do all sorts of concoctions. Not only the magic potions kids do with mud  and dishwashing liquid. But all sorts of potable drinks that a mixologist may experiment with. There wasn’t any alcohol in those drinks, but the principle was the same. Some of them were good enough for my tastes. But I never achieved the kind of breakthrough drink which would please masses. I did, however, got my experimentation spirit to bear on food.

By age nine, I was cooking for myself at lunch. Nothing very elaborate, maybe. It often consisted of reheating leftovers. But I got used to the stove (we didn’t have a microwave oven, at the time). And I sometimes cooked some eggs or similar things. To this day, eggs are still my default food.

And, like many children, I occasionally contributing to cooking. Simple things like mixing ingredients. But also tasting things at different stages in the cooking or baking process. Given the importance of sensory memory, I’d say the tasting part was probably more important in my development than the mixing. But the pride was mostly in being an active contributor in the kitchen.

Had I understood fermentation as a kid, I probably would have been fascinated by it. In a way, I wish I could have been involved in homebrewing at the time.

A homebrewery is an adult’s chemistry set.

Beer Eye for the Coffee Guy (or Gal)

Judged twelve (12) espresso drinks as part of the Eastern Regional Canadian Barista Championship (UStream).

[Never watched Queer Eye. Thought the title would make sense, given both the “taste” and even gender dimensions.]

Had quite a bit of fun.

The experience was quite similar to the one I had last year. There were fewer competitors, this year. But I also think that there were more people in the audience, at least in the morning. One possible reason is that ads about the competition were much more visible this year than last (based on my own experience and on several comments made during the day). Also, I noticed a stronger sense of collegiality among competitors, as several of them have been different things together in the past year.

More specifically, people from Ottawa’s Bridgehead and people from Montreal’s Café Myriade have developed something which, at least from the outside, look like comradery. At the Canadian National Barista Championship, last year, Myriade’s Anthony Benda won the “congeniality” prize. This year, Benda got first place in the ERCBC. Second place went to Bridgehead’s Cliff Hansen, and third place went to Myriade’s Alex Scott.

Bill Herne served as head judge for most of the event. He made it a very pleasant experience for me personally and, I hope, for other judges. His insight on the championship is especially valuable given the fact that he can maintain a certain distance from the specifics.

The event was organized in part by Vida Radovanovic, founder of the Canadian Coffee & Tea Show. Though she’s quick to point to differences between Toronto and Montreal, in terms of these regional competitions, she also seemed pleased with several aspects of this year’s ERCBC.

To me, the championship was mostly an opportunity for thinking and talking about the coffee world.

Met and interacted with diverse people during the day. Some of them were already part of my circle of coffee-loving friends and acquaintances. Some who came to me to talk about coffee after noticing some sign of my connection to the championship. The fact that I was introduced to the audience as a blogger and homeroaster seems to have been relatively significant. And there were several people who were second-degree contacts in my coffee-related social network, making for easy introductions.

A tiny part of the day’s interactions was captured in interviews for CBC Montreal’s Daybreak (unfortunately, the recording is in RealAudio format).

“Coffee as a social phenomenon” was at the centre of several of my own interactions with diverse people. Clearly, some of it has to do with my own interests, especially with “Montreal’s coffee renaissance.” But there were also a clear interest in such things as the marketshare of quality coffee, the expansion of some coffee scenes, and the notion of building a sense of community through coffee. That last part is what motivated me to write this post.

After the event, a member of my coffee-centric social network has started a discussion about community-building in the coffee world and I found myself dumping diverse ideas on him. Several of my ideas have to do with my experience with craft beer in North America. In a way, I’ve been doing informal ethnography of craft beer. Beer has become an area of expertise, for me, and I’d like to pursue more formal projects on it. So beer is on my mind when I think about coffee. And vice-versa. I was probably a coffee geek before I started homebrewing beer but I started brewing beer at home before I took my coffee-related activities to new levels.

So, in my reply on a coffee community, I was mostly thinking about beer-related communities.

Comparing coffee and beer is nothing new, for me. In fact, a colleague has blogged about some of my comments, both formal and informal, about some of those connections.

Differences between beer and coffee are significant. Some may appear trivial but they can all have some impact on the way we talk about cultural and social phenomena surrounding these beverages.

  • Coffee contains caffeine, beer contains alcohol. (Non-alcoholic beers, decaf coffee, and beer with coffee are interesting but they don’t dominate.) Yes: “duh.” But the difference is significant. Alcohol and caffeine not only have different effects but they fit in different parts of our lives.
  • Coffee is often part of a morning ritual,  frequently perceived as part of preparation for work. Beer is often perceived as a signal for leisure time, once you can “wind down.” Of course, there are people (including yours truly) who drink coffee at night and people (especially in Europe) who drink alcohol during a workday. But the differences in the “schedules” for beer and coffee have important consequences on the ways these drinks are integrated in social life.
  • Coffee tends to be much less expensive than beer. Someone’s coffee expenses may easily be much higher than her or his “beer budget,” but the cost of a single serving of coffee is usually significantly lower than a single serving of beer.
  • While it’s possible to drink a few coffees in a row, people usually don’t drink more than two coffees in a single sitting. With beer, it’s not rare that people would drink quite a few pints in the same night. The UK concept of a “session beer” goes well with this fact.
  • Brewing coffee takes a few minutes, brewing beer takes a while (hours for the brewing process, days or even weeks for fermentation).
  • At a “bar,” coffee is usually brewed in front of those who will drink it while beer has been prepared in advance.
  • Brewing coffee at home has been mainstream for quite a while. Beer homebrewing is considered a hobby.
  • Historically, coffee is a recent phenomenon. Beer is among the most ancient human-made beverages in the world.

Despite these significant differences, coffee and beer also have a lot in common. The fact that the term “brew” is used for beer and coffee (along with tea) may be a coincidence, but there are remarkable similarities between the extraction of diverse compounds from grain and from coffee beans. In terms of process, I would argue that beer and coffee are more similar than are, say, coffee and tea or beer and wine.

But the most important similarity, in my mind, is social: beer and coffee are, indeed, central to some communities. So are other drinks, but I’m more involved in groups having to do with coffee or beer than in those having to do with other beverages.

One way to put it, at least in my mind, is that coffee and beer are both connected to revolutions.

Coffee is community-oriented from the very start as coffee beans often come from farming communities and cooperatives. The notion, then, is that there are local communities which derive a significant portion of their income from the global and very unequal coffee trade. Community-oriented people often find coffee-growing to be a useful focus of attention and given the place of coffee in the global economy, it’s unsurprising to see a lot of interest in the concept (if not the detailed principles) of “fair trade” in relation to coffee. For several reasons (including the fact that they’re often produced in what Wallerstein would call “core” countries), the main ingredients in beer (malted barley and hops) don’t bring to mind the same conception of local communities. Still, coffee and beer are important to some local agricultural communities.

For several reasons, I’m much more directly involved with communities which have to do with the creation and consumption of beverages made with coffee beans or with grain.

In my private reply about building a community around coffee, I was mostly thinking about what can be done to bring attention to those who actually drink coffee. Thinking about the role of enthusiasts is an efficient way to think about the craft beer revolution and about geeks in general. After all, would the computer world be the same without the “homebrew computer club?”

My impression is that when coffee professionals think about community, they mostly think about creating better relationships within the coffee business. It may sound like a criticism, but it has more to do with the notion that the trade of coffee has been quite competitive. Building a community could be a very significant change. In a way, that might be a basis for the notion of a “Third Wave” in coffee.

So, using my beer homebrewer’s perspective: what about a community of coffee enthusiasts? Wouldn’t that help?

And I don’t mean “a website devoted to coffee enthusiasts.” There’s a lot of that, already. A lot of people on the Coffee Geek Forums are outsiders to the coffee industry and Home Barista is specifically geared toward the home enthusiasts’ market.

I’m really thinking about fostering a sense of community. In the beer world, this frequently happens in brewclubs or through the Beer Judge Certification Program, which is much stricter than barista championships. Could the same concepts apply to the coffee world? Probably not. But there may still be “lessons to be learnt” from the beer world.

In terms of craft beer in North America, there’s a consensus around the role of beer enthusiasts. A very significant number of craft brewers were homebrewers before “going pro.” One of the main reasons craft beer has become so important is because people wanted to drink it. Craft breweries often do rather well with very small advertising budgets because they attract something akin to cult followings. The practise of writing elaborate comments and reviews has had a significant impact on a good number of craft breweries. And some of the most creative things which happen in beer these days come from informal experiments carried out by homebrewers.

As funny as it may sound (or look), people get beer-related jobs because they really like beer.

The same happens with coffee. On occasion. An enthusiastic coffee lover will either start working at a café or, somewhat more likely, will “drop everything” and open her/his own café out of a passion for coffee. I know several people like this and I know the story is quite telling for many people. But it’s not the dominant narrative in the coffee world where “rags to riches” stories have less to do with a passion for coffee than with business acumen. Things may be changing, though, as coffee becomes more… passion-driven.

To be clear: I’m not saying that serious beer enthusiasts make the bulk of the market for craft beer or that coffee shop owners should cater to the most sophisticated coffee geeks out there. Beer and coffee are both too cheap to warrant this kind of a business strategy. But there’s a lot to be said about involving enthusiasts in the community.

For one thing, coffee and beer can both get viral rather quickly. Because most people in North America can afford beer or coffee, it’s often easy to convince a friend to grab a cup or pint. Coffee enthusiasts who bring friends to a café do more than sell a cup. They help build up a place. And because some people are into the habit of regularly going to the same bar or coffee shop, the effects can be lasting.

Beer enthusiasts often complain about the inadequate beer selection at bars and restaurants. To this day, there are places where I end up not drinking anything besides water after hearing what the beerlist contains. In the coffee world, it seems that the main target these days is the restaurant business. The current state of affairs with coffee at restaurants is often discussed with heavy sighs of disappointment. What I”ve heard from several people in the coffee business is that, too frequently,  restaurant owners give so little attention to coffee that they end up destroying the dining experience of anyone who orders coffee after a meal. Even in my own case, I’ve had enough bad experiences with restaurant coffee (including, or even especially, at higher-end places) that I’m usually reluctant to have coffee at a restaurant. It seems quite absurd, as a quality experience with coffee at the end of a meal can do a lot to a restaurant’s bottom line. But I can’t say that it’s my main concern because I end up having coffee elsewhere, anyway. While restaurants can be the object of a community’s attention and there’s a lot to be said about what restaurants do to a region or neighbourhood, the community dimensions of coffee have less to do with what is sold where than with what people do around coffee.

Which brings me to the issue of education. It’s clearly a focus in the coffee world. In fact, most coffee-related events have some “training” dimension. But this type of education isn’t community-oriented. It’s a service-based approach, such as the one which is increasingly common in academic institutions. While I dislike customer-based learning in universities, I do understand the need for training services in the coffee world. What I perceive insight from the beer world can do is complement these training services instead of replacing them.

An impressive set of learning experiences can be seen among homebrewers. From the most practical of “hands-on training” to some very conceptual/theoretical knowledge exchanges. And much of the learning which occurs is informal, seamless, “organic.” It’s possible to get very solid courses in beer and brewing, but the way most people learn is casual and free. Because homebrewers are organized in relatively tight groups and because the sense of community among homebrewers is also a matter of solidarity.  Or, more simply, because “it’s just a hobby anyway.”

The “education” theme also has to do with “educating the public” into getting more sophisticated about what to order. This does happen in the beer world, but can only be pulled off when people are already interested in knowing more about beer. In relation with the coffee industry, it sometimes seems that “coffee education” is imposed on people from the top-down. And it’s sometimes quite arbitrary. Again, room for the coffee business to read the Cluetrain Manifesto and to learn from communities.

And speaking of Starbucks… One draft blogpost which has been nagging me is about the perception that, somehow, Starbucks has had a positive impact in terms of coffee quality. One important point is that Starbucks took the place of an actual coffee community. Even if it can be proven that coffee quality wouldn’t have been improved in North America if it hadn’t been for Starbucks (a tall order, if you ask me), the issue remains that Starbucks has only paid attention to the real estate dimension of the concept of community. The mermaid corporation has also not doing so well, recently, so we may finally get beyond the financial success story and get into the nitty-gritty of what makes people connect through coffee. The world needs more from coffee than chains selling coffee-flavoured milk.

One notion I wanted to write about is the importance of “national” traditions in both coffee and beer in relation to what is happening in North America, these days. Part of the situation is enough to make me very enthusiastic to be in North America, since it’s increasingly possible to not only get quality beer and coffee but there are many opportunities for brewing coffee and beer in new ways. But that’ll have to wait for another post.

In Western Europe at least, coffee is often associated with the home. The smell of coffee has often been described in novels and it can run deep in social life. There’s no reason homemade coffee can’t be the basis for a sense of community in North America.

Now, if people in the coffee industry would wake up and… think about actual human beings, for a change…