The shape of last week’s discussion was largely determined by the format of class: presentations on McLuhan’s different case studies. I’ve done this sort of exercise before with students in reference to McLuhan, but I thought last Thursday’s class was exceptionally successful. We covered a lot of ground, learned a lot together, and I think you guys demonstrated an admirable grasp of the material while also wrestling with McLuhan’s many, many problems.
What to prepare for our next class:
A few notes: * First of all, thanks so very, very much for taking up the slack on Slack (yuk yuk) while I was out of town, giving a lecture.
I want to reflect a bit on our lab last night.
What to expect in class and lab for January 21:
Thank you for bearing with me on Thursday as the technology broke. (Technology always breaks.)
I have now sent out invitations for all of you to join our ENG 7006 Slack team. Slack is pretty self-explanatory, especially if you do some poking around and watch the getting started tutorial. But I want to make sure you notice a few things:
This post is meant to document, and preview, some of the tech setup we’ll need to do at the beginning of the semester. What every student will need to do: 1. Sign up for a GitHub account. This can be done right at GitHub’s home page.
A quick note: our coding lessons are, in fact, live. They live at:
Welcome to ENG 7006! I don’t have much to say now, but keep following the blog to keep up with developments, including Feedly information, responses to commonly asked questions, changes and developments, weeks-in-review written by Scott, and other good stuff. I’ll probably also write about some things that are of interest to me as we go along.
This semester, we’ll be blogging with Jekyll, a hacker-ish blogging platform. This is explicitly designed to get you “close to the metal,” using our coding tools for blogging, too: GitHub and Atom.