Skip to content

Instantly share code, notes, and snippets.

@remixz
Created February 24, 2016 01:13
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
Star You must be signed in to star a gist
Save remixz/24393820b2a31d917efd to your computer and use it in GitHub Desktop.

notes

passing thoughts

  • this workshop says to sign up jsbin if i haven't already. i think this is an older workshop. we should update them all to either cloud9 or jsbin.
  • inconsistency in code example. in the first step, it says the line is createCanvas(300, 500);, but the jsbin that you use is createCanvas(250, 500);. nitpick
  • this is detailed. i like it. there's definitely no room for confusion so far.
  • actually, one thing. where are we getting these variables like mouseX? we should note, maybe at the start, that these kind of variables aren't in every piece of code, and are part of the libraries we're using. (in this case, p5.play.js)
  • on mouse movement, there's a few typos. reminder for myself to proofread.
  • when in the console, we remove the ball with ball.remove(), then it says to do ball.overlap(goal);. only problem is that we never actually get the ball back! we should add a note on how to get the ball back. i hit the "run with js" button to get it back.
  • Yay you finished the Linear Tutorial! - probably should change it to something like the soccer tutorial, for consistency.

post-workshop thoughts

  • kind of feels incomplete without part 2 being fully written. i think some of the ideas from the planned part 2 should just be added to part 1. namely, adding a score counter, and maybe the second goal and player.
  • SONIC BOOM http://jsbin.com/daxeza
  • definitely a solid tutorial in terms of someone new to coding. lots of important game concepts taught.
  • there's more game tutorials to go, though. i had mentioned this in my original interview with zach, but i feel like the curriculum is a bit heavy on the game stuff. i'd rather condense it down into one or two tutorials, and try to introduce some new concepts that explore more of computer science. i'd hate for these clubs to be boiled down to "video game making club", since it could be so much more.
  • alternatively, we just offer this one game as an intro to game-making, and we move the rest of the tutorials to a pathway for people interested in games. basically, the first few meetings of a club, everyone would do the same things, so that everyone is introduced to new things, and then after they've done a little taste of all we have to offer, someone can choose to specialize in an area for a little bit.
  • one disadvantage to segmenting is if that, let's say, 90% of the club wants to do one thing, and 10% want to do another, then those 10% might feel kind of left out. don't want that. needs discussion!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment