DGMD S-15

Weekly session summaries

13: Farewell!
3 August 2016
Slides for Session 13

Farewell!

For next session

  1. Please keep in touch!! 💌 And never hesitate to ask to meet up or chat…

12: Prepping a final presentation
1 August 2016
Slides for Session 12

sharing out your presentation in small groups • our last studio time!

For next session

  1. Email us a link to your presentation by midnight Tuesday.
  2. Email us up-to-date links to your journal and your /people card, if we haven't received them from you yet (we'll be in touch).
  3. If you aren't presenting to the group Wednesday, email us to schedule a time to sit down and present to us as a small group.
  4. Email us to find a time to sit down and debug, brainstorm your presentation, or work through any other, remaining questions.

11: Objects, data, & circles
27 July 2016
Slides for Session 11

drawing circles • different ways of representing circles • pair programming infographics • studio time

For next session

  1. Come in with some version of a functional demo/presentation on Monday to share-out/test with a partner.
  2. Make sure we have up-to-date links to your journal and your /people card, if we haven't received them from you yet.
  3. Answer the usual questions for your project in your journal:
    1. What did you accomplish today?
    2. What do you aim to have done by next session?
    3. What can we (the teaching team) do to help?
  4. If you get stuck, submit a Code Snippet Request or get in touch on Slack if you have any trouble!

10: Final presentations, stories, & slides
25 July 2016
Slides for Session 10

exemplar final presentations • stories vs. demos • reveal.js • studio time

For next session

  1. Make sure the current state of your project(s) is posted online somewhere (e.g. using GitHub Pages) and make sure a link to it is posted on your journal. (Of course, we know the project isn't yet done! We want to make sure you have a workflow set up that will allow you to go live when you need to!)
  2. Post a first draft outline for your final presentation — in words, sketches, or skeletal slides. (Of course, we know the slides aren't yet done either!)
  3. Answer the usual questions for your project in your journal:
    1. What did you accomplish today?
    2. What do you aim to have done by next session?
    3. What can we (the teaching team) do to help?
  4. If you get stuck, submit a Code Snippet Request or get in touch on Slack if you have any trouble!

9: Inputs, outputs, & Arduinos
18 July 2016
Slides for Session 9

inputs & outputs • Arduino <> HTML • studio time

For next session

  1. Let us know if you'd like to meet up about your project! We want to make sure you feel good about where you end up in four weeks 🎉🎉🎉
  2. Post your code to your journal along with your black box diagram and any other notes or materials you used.
  3. Answer the usual questions in your journal:
    1. What did you accomplish today?
    2. What do you aim to have done by next session?
    3. What can we (the teaching team) do to help?
  4. If you get stuck, submit a Code Snippet Request or get in touch on Slack if you have any trouble!

8: Inputs, outputs, & black boxes
18 July 2016
Slides for Session 8

inputs & outputs • black boxes & flow-charts • an intro to physical computing • studio time

For next session

  1. Post your code to your journal along with your black box diagram and any other notes or materials you used.
  2. In addition, post some physical inputs you think might make for an interesting visualization using one of the sketches we looked at today.
  3. Also answer the usual questions in your journal:
    1. What did you accomplish today?
    2. What do you aim to have done by next session?
    3. What can we (the teaching team) do to help?
  4. If you get stuck, submit a Code Snippet Request or get in touch on Slack if you have any trouble!

7: Workshopping your project
13 July 2016
Slides for Session 7

brainstorming next questions • small-group workshopping • studio time

For next session

  1. Share out notes and next steps from your brainstorm today in your journal
  2. Also in your journal, answer:
    1. What did you accomplish today?
    2. What do you aim to have done by next session?
    3. What can we (the teaching team) do to help?
  3. If you get stuck, submit a Code Snippet Request or get in touch on Slack if you have any trouble!

6: Pairing, JavaScript, and CSS animations
11 July 2016
Slides for Session 6

small projects • a couple, HTML/CSS/JS effects • time for pair programming • studio time

For next session

  1. In your journal, answer these questions:
    1. What did you accomplish today?
    2. What do you aim to have done by next session?
    3. What can we (the teaching team) do to help
  2. Work to actually accomplish the goal you set for yourself.
  3. If you get stuck, submit a Code Snippet Request or get in touch on Slack if you have any trouble!

5: APIs, pomes, & pair programming
6 July 2016
Slides for Session 5

using the Flickr API, a technical walkthrough • sharing our project mock-ups • time for pair programming • studio time

For next session

  1. In your journal, answer these questions:
    1. What did you accomplish today?
    2. What do you aim to have done by next session?
    3. What can we (the teaching team) do to help
  2. Work to actually accomplish the goal you set for yourself.
  3. If you get stuck, submit a Code Snippet Request or get in touch on Slack if you have any trouble!
  4. Please read these pair programming articles before next session. Often people think pair programming will go more slowly than "just" doing it yourself. Often this is not true. We encourage you to reach out to friends and acquaintences in the class, through Slack if you'd like, to pair program over the break and weekend.

4: Mock-ups, more pomes, and an intro
29 June 2016
Slides for Session 4

talking about mock-ups, story maps, & specs • an intro to HTML, CSS, and JavaScript • setting up the pomes project locally, and poking around in it • studio time for coding & spec-ing

For next session

  1. Post a mock-up (or story map or spec) and description of your personal project to your journal. If you aren't yet feeling generative, please get in touch with us to brainstorm! (We don't want you to work on something you think is lame!)
  2. Take a go at messing around with the pomes project, whether with the extensions we've suggested or by making it your own in your own way.
  3. Submit a Code Snippet Request or get in touch on Slack if you have any trouble!

    4. If you just want some more stuff to explore...

  4. If you want to get started with HTML, CSS, and JavaScript, you might check out the Tools & Materials page. We suggest starting with our own intro to and demo of the basics of HTML/CSS/JS. Then, we recommend Shay Howe's Learn to Code HTML & CSS and the online book series You Don't Know JS.

3: Intro to pomes & personal projects
27 June 2016
Slides for Session 3

looking at cool digital stuff • mocking up the pomes project • thinking about design constraints and specifications • personal projects & mock-ups

For next session

  1. If you haven't already: Make sure your journal is live on GitHub pages, your /people card is posted there, and your machine has the course dependencies installed.
  2. Before Wednesday's session: Begin thinking about the many different ways you can sketch and specify a project: We will be looking for your own mock-up by the end of this week.
  3. Submit a Code Snippet Request or get in touch on Slack if you have any trouble!

    4. If you just want some more stuff to explore...

  4. If you want to get started with HTML, CSS, and JavaScript, you might check out the Tools & Materials page. We suggest starting with our own intro to and demo of the basics of HTML/CSS/JS. Then, we recommend Shay Howe's Learn to Code HTML & CSS and the online book series You Don't Know JS.

2: Journals, code snippets, & /people cards
22 June 2016
Slides for Session 2

setting up our GitHub Pages journals • a little about git and GitHub • what are code snippets and how can you request them? • studio time for building our /people cards

For next session

  1. By Sunday evening: Post a link to a digital thing you love to your journal. Whether you think it's beautiful, clever, powerful, hilarious, etc.
  2. By Monday's session: Finish setting up a DGMD S-15 journal using GitHub pages. You can style them as little or much as you'd like. Here are some journals by last semester's participants.
  3. By Monday's session: Finish a first draft of your partner's /people card including at least their name, a new picture, and their GitHub username. Post it to your journal! You should also take a go at implementing the effect to represent them, looking at the people page on last semester's class site for some ideas or this library of basic effects for inspiration.
  4. By Monday's session: Finish setting up your local development environment by following these steps. If you run into trouble, don't stress (or stay up all night). We'll be available to make sure you're set up. We'll be using many of these tools Monday, so please reach out before then if you are having any trouble!
  5. Submit a Code Snippet Request or get in touch on Slack if you are having trouble with any of these steps!

    6. If you just want some more stuff to explore...

  6. If you want to get started with HTML, CSS, and JavaScript, you might check out the Tools & Materials page and Shay Howe's Learn to Code HTML & CSS. We'll also be digging into our own intro to and demo of the basics of HTML/CSS/JS, which might be of particular use.
    7. </ol>

1: The first session
20 June 2016
Slides for Session 1

why do we code? • getting to know someone in the course • designing digital effects to representthem in a digital card in Codepen to live on the people page of our course site

For next session

  1. Make at least three sketches representing effects you'd like to add to your partner's card and have them choose one to represent them on the course website. We'll be posting them to a personal journal hosted on GitHub, which we'll ask you to use as your central place for keeping materials. If you'd like to get a headstart, check out these directions.
  2. We'll be using Slack (tour here) as our course chat room, which you can join here.
  3. Take a go at setting up up your local development environment by following these steps. If you run into trouble, don't stress (or stay up all night). We'll be available to make sure you're set up.

    4. If you just want some more stuff to explore...

  4. Check out our /people card template and start transforming it to represent your partner. Make your own account, fork our sketch, and replace Kanye with your partner, adding a CSS or Javascript effect of your own. You can look at the people page on last semester's class site for some ideas or use this library of basic effects for inspiration.
  5. If you want to get started with HTML, CSS, and JavaScript, you might check out the Tools & Materials page and Shay Howe's Learn to Code HTML & CSS. We'll also be digging into our own intro to and demo of the basics of HTML/CSS/JS, which might be of particular use.