51 things every game student should know

Recommendations

Info

Just because it doesn’t have the word GAMES in it, doesn’t mean it’s not going to inspire, inform or be useful to you <strong>every</strong> day for the rest of your creative life. This is especially true of non‐electronic information such as: • Books • Museums • Art • History Kaye Elling @K_0, Spring 2013
A good rule of thumb for selecting work for your portfolio is this: “If someone who didn’t <strong>know</strong> me saw this work, would they think I was a serial killer?” Kaye Elling @K_0, Spring 2013
Page 1 and 2: 51 things every game student should
Page 3 and 4: Quad: face with 4 sides Triangle: f
Page 5 and 6: Polycount: It’s a target, not a l
Page 7 and 8: Developers don’t say “mobs”.
Page 9 and 10: Game development is a team sport fo
Page 11 and 12: Don’t break the fourth wall in as
Page 13 and 14: The things you say, may say more ab
Page 15 and 16: Read the brief. No, seriously: READ
Page 17 and 18: Your first year at uni should be re
Page 19 and 20: Understand Brightness & Contrast Ka
Page 21 and 22: IF YOU AREN’T CONFIDENT IN YOUR W
Page 23 and 24: Be inclusive: Don’t assume the de
Page 25 and 26: Also: Usability Testing: Getting ta
Page 27 and 28: Also: Quality Assurance: A complete
Page 29 and 30: Most developers work in shared spac
Page 31 and 32: Attention to detial. It matters. Ka
Page 33 and 34: Your final year at uni should be re
Page 35: Nobody gets everything right first
Page 39 and 40: Project management: Not just for ma
Page 41 and 42: At a job interview, remember that y
Page 43 and 44: Duz not luk gud on ur work. Like ev
Page 45 and 46: When you get some feedback: Heed it
Page 47 and 48: “Dear Sir or Madam, I’m a recen
Page 49 and 50: If your game idea starts with the s
Page 51 and 52: The office is not like the internet
Page 53: Kaye Elling is the grizzled veteran

51 things every game student should know

Create successful ePaper yourself

Delete template?

Save as template?