teaching
CMSC 336
Games Systems: Platforms, Programs & Power (S2022)
overview | logistics | schedule | assignments | github | resources
|
|
|
Class: Mon & Wed 3:10-4:30pm (RKC 107)
Office Hours: Mon 11am-12pm & Thu 10-11am and by appointment (RKC 204)
Platform Study Texts
- 10 PRINT CHR$(205.5+RND(1)); : GOTO 10. Montfort, Baudoin, Bell, Bogost, Douglass, Marino, Mateas, Reas, Sample, and Vawter. MIT Press. 2012.
- Racing the Beam. Montfort and Bogost. MIT Press. 2009.
- I am Error. Altice. MIT Press. 2015.
- Game Programming Patterns. Nystrom. 2014.
- Making Games for the Atari 2600. Hugg. 2018.
- Making Games for the NES. Hugg. 2018.
- Programming in Lua. 3rd or 4th Edition. Roberto Ierusalimschy. 2016.
- 21st Century C (2nd Edition) by Ben Klemens. O'Reilly. 2015.
- Projects (60%): Four projects (remake/hack/demake/make)
- Assignments (20%): Small programming assignments and homework
- Participation (20%): Discussion and quizzes (every class)
- Participate. There will be myriad opportunities: in RKC 107, google docs, github, dropbox paper, excalidraw, office hours, discord.
- When reading, studying, and listening, be active by taking notes and asking questions.
- Visit the professor's and tutor's drop-in hours.
- Attend class & be on time (whenever possible given COVID reality).
- Make sure to have read the required reading BEFORE class.
- Start all the assignments early.
- Check Google Classroom & this class website.
- Be respectful of your fellow classmates; my rule of thumb for judging whether a response is worthwhile: Is it Nice? Is it True? Is it Necessary? Pick at least two.
- Adhere to the Code of Ethics and Professional Conduct for the Association for Computing Machinery.
- Cooperate carefully and thoughtfully:
- Work within your pair & pod, and visit drop-in hours, before seeking help beyond.
- Credit work, including all sources you used from the web, other books, etc.
- Sharing ideas is encouraged, but blatantly copying work without attribution will be treated as scholastic dishonesty and receive no credit.
- Be prepared to demonstrate the theory of your program (Peter Naur).
- Keep your work backed-up and private using Google drive.