(no subject)

[prog]

Even in this startup mode, I think I need to take a day off at least once a week. Yesterday was that day for me, though I refused to admit it until bedtime. After the shoot I returned home to work, and while I did do a little I mostly farted around online for 10 hours. (Some of that was me diving headfirst into the /davis_?square/ mess, which I actually consider to be time well spent, but mostly it was around-farting.)

---

Oo oo I just got a good idea for a Gamshelf side-project: Jmac's Guide to Teaching Games. A short video illustrating my personal principles of good board game teaching, contrasted with my observations of well-meaning-but-ineffective teaching. This was inspired by a thread on BGG where I witnessed people complaining about how nobody ever listens when they teach a game by reading its rules out loud, to which I say, "You're reading the rules of a game out loud?!"

I would like to use a "goofus and gallant" format, but am not sure whether I should be in one role, or both, or neither. The most "obvious" choice to me involves me playing the Good Teacher and casting "evil jmac" (me w/ glued-on goatee or Dali 'stache or something) as the Bad Teacher but that's kind of a tired joke so I don't know.

It would be entirely scripted, making it a fun new challenge for me. (The Gameshelf's host segments are only lightly scripted, which is unfortunately evidenced by the thus-far strained nature of my monologues. I need to improve this.)

Comments

[jtroutman.livejournal.com]

A day off is a good thing. You will fail from burnout if you do not. (This is the voice of experience here, sonny! *cough* Now, where's my walker?).

I think that Jmac's Guide to Teaching Games would be fantastic to do, especially downloadable over the internets. And, wow.. you could even actually go so far as to make instructional videos for certain games (or to produce them for game companies.. hmm hmm).

Remember.

[kyroraz.livejournal.com]

All work and no play makes prog a dull boy.

You need a day off. Once a week. Really.

[radtea.livejournal.com]

After the shoot I returned home to work, and while I did do a little I mostly farted around online for 10 hours.

Spot the entrepreneur: "After a bunch of work one day, I took some time off. I'm calling that a day off..." :-)

Every study of every industry for the past 100 years has shown that the most productive work-week is 35 to 40 hours. Yet people persist in thinking that long hours are good. They aren't, unless you're dedicated to low productivity. In start-up mode they are sometimes necessary--I don't want to think about the number of hours I logged last week between client meetings and technological surprises--but the goal should always be to work fewer hours, more productively.

In my former company my business partners were very dedicated to the "more-hours-are-better" school of idiocy, and I could never convince them my way was better, despite bringing more revenue to the company than them. Some people just aren't capable of learning.

So a day a week off is a great idea, even in startup-mode. Now that I'm running my own show I've been taking two half-days most weekends, and I can really feel the positive effects from getting that break.

[karlvonl.livejournal.com]

I know at least one person whose approach to teaching games is often to read the rules out loud, and I've found that it's not such a bad approach after all, and have occasionally adopted that approach myself. The reasoning is that, there's no a priori reason to assume that the person teaching the game can come up with a more clear and concise explanation of the rules, improvised on the spot, than what's contained in the actual published rulebook. Of course, the manner of reading can be a help or hinderance. Varied vocal inflection, occasional pauses to let things sink in or even for some discussion of what was just read, and judicious skipping of redundant material, can be helpful.

[prog.livejournal.com]

The reasoning is that, there's no a priori reason to assume that the person teaching the game can come up with a more clear and concise explanation of the rules, improvised on the spot, than what's contained in the actual published rulebook.

I consider the rules to exist primarily as an ultimate reference that's handy to have at the table. As far as teaching rules goes, though, I see the rulebook more as a "seed" that imparts the game's rules to one who hasn't had the opportunity to be taught the game by someone else. Person-to-person game-teaching can and should be a far more interactive experience than a textbook lecture.

I know that when I want to play, nothing is more boring than being read to, especially when there are happy colorful bits lying around. This leads to the BGG thread of people honestly confused why their dumb newbie friends would rather stack their meeples into pyramids than listen to them read the rules. There is hostility there towards people who say "How about we just start and I'll pick it up," which is unfortunate, since this is exactly what I usually say when I find myself stuck listening to someone earnestly recite a rulesheet at me.

My approach avoids either situation by using the game's bits to improvise illustrations as you go over the rules, which is significantly less boring than plain reading.

[greenlily.livejournal.com]

As someone who usually has to have games explained to her, I second the guide-to-teaching-games plan. There are few things that suck harder than being 'taught' a game by someone whose idea of teaching is to read the rules out loud and periodically interject "...but we never actually do that...".

Examples!

[radtea.livejournal.com]

Whenever my kids and I are learning a new game we read the rules and try to come up with examples as we go, working with the gamepieces. Like dropping a nuke from orbit: it's the only way to be sure...