Frequently Asked Questions

Weekly Structure

Q: How often are we supposed to blog?
A: The minimum you should do for your blog is discussed on post 182. Also my recent post 246 discussing each person's blog should be helpful.
Check each person's blog and see my comments. That way you get to know everybody in the class! :-) My own blog for the class shows the minimum.

Ideally you run a blog like Keith's which has an ongoing discussion of what you have tried, what worked, what didn't etc.
I also ran a blog like this last year on a project I worked on with another person last year: http://www.livejournal.com/~soundblocks
I recognize that expecting a blog like Keith's or mine might be too much to require for the class, but the purpose of the blog should be clear from these examples.

In terms of how often to blog, what I suggest is that every time you sit down at your computer to work on Pd or the Logochip or anything else from the class, open up a browser to your blog so you are ready to post.
If something comes up that will help you document your work or your mistakes, or be helpful in any way to you or anybody else, put it in the blog. It's a 2 second inconvenience that will have huge dividends.
I would expect at an absolute minimum of 1 post/week to match the assignment you did. This is a minimum.

Q: Do our Pd files need to go on our blog site?
A: Yes. Post them on the wiki and link to them from your blog. You can't literally post them directly on the blog. Wordpress won't let you.

Q: What are we supposed to be talking about in our weekly pairings?
A:

1. Whatever was discussed for the week. Make sure both people completely understand the material and can do the assignment.

Perhaps even do the assignment together, at least in part. For example, with the Pd stuff, making sure both people are comfortable with Pd. Try Pd. Do the "hello world" assignment together.

1. Final project ideas. Brainstorm about your idea with the other person. See if there is some common ground. Keep in mind that you will need a partner for your final project idea. Discuss what is an exciting idea, what is a possible idea, etc.
2. See if there is something in your expertise that your partner would like to learn about. See if there is something in their expertise that you would like to learn about.
3. After you meet with them, send me 2-3 sentences addressing each of these 3 things.

Final Projects

Q: How do you want final projects organized? We talked in class about splitting Shift-Space into areas by category, e.g. motion, water, light, sound, etc.
A: Sounds exciting! It's up to the class. How can I help facilitate a class decision?

Q: I have heard a rumor that we are going to be in pairs for groups???
A: It's not a rumor. It's in the syllabus. :-)

Q: How large will the groups be? It seems like fewer than four people would have trouble getting a project finished in time to exhibit at Shift-Space.
A: Yes I was thinking 2-3 people per group. It's not the first time somebody has suggested this is too small a group.
I feel flexible about it. I just want to make sure that everybody in the group pulls their weight and at least understands and is able to speak intelligently about every part of the project, even if they did not directly build it.
That said, a group of 4 could be possible.