Project details will change once the Slack bot is up and running

Projects are simple. Up to two weeks of work, published online, success or failure, supported by instructors and other students.

Please note: no one cares if your code sucks.

Why so quick?

Because working on one project for a long time doesn’t teach you anything, especially if you’re new to the game. As Gene Wolfe said to Neil Gaiman,

“You never learn how to write a novel,” he said. “You just learn how to write the novel that you’re writing.”

Data ain’t no different.

The Schedule

  1. Wednesday: Pitch
  2. Wednesday: Feedback
  3. Friday: Tutorial hunting
  4. Wednesday: First draft + feedback
  5. Saturday: Second draft (optional)
  6. Wednesday: Final draft

Read more on the schedule page

Project Content

Most projects will have two pieces, the story itself (words) and some method of presentation.

Your presentation can be paragraphs of texts, an interactive piece, a static map, a series of photographs, or a fancy scrollytelling site.

The only important part of a project is make sure it’s something you’re interested in making.

(And it should hopefully involve some sort of data. But hey, if you want to make a Slack bot I won’t complain.)

Getting help and questions answered

As in #projects in Slack, even if it’s something hyper-specific to your project. I want everyone to see everyone else’s questions, and someone might be struggling with the exact same issue.

We can take it to direct messages once it becomes an Ordeal for everyone else to see it.