Read on Twitter
I’m back, because this is too good a thing not to thread: stuff I wish classes would teach students, and often don’t... https://twitter.com/nicholestrano/status/1302346416757641217">https://twitter.com/nicholest...
Source control. My god. It’s baffling that you don’t have students set up on a repository and learning (through mess ups) how to be a good collaborator in that process.
Stop telling students they need to be able to do 200 page GDDs. They need to be able to write two pages on a proposal for a design system, but nobody is asking the junior designer to write the GDD, and the vast majority of studios stopped writing docs nobody reads 10 yrs ago.
No, we don’t use wikis either. Stop it.
Stop setting your students the graded task of interviewing a ‘noteworthy’ developer.
a) it’s unscalable, Relatively known devs get an impossible number of requests
b) you’re not training journalists
c) efficient research is core to dev. Teach them how to google better instead
a) it’s unscalable, Relatively known devs get an impossible number of requests
b) you’re not training journalists
c) efficient research is core to dev. Teach them how to google better instead
d) anyone they’ve heard of has likely already done 50 podcasts and 5 gdc talks. They’ve definitely answered the question of ‘how did you get into game dev’
Teach paths other than ‘solo indie’ and ‘employee 500 on a AAA’. Most first jobs are neither, and students should be equipped better for the bulk of entry level jobs. And for the likely lack of glamour.
Don’t spend lesson time on technical tutorials. You are not as good at it as YouTube is. Instead, teach process, creative problem solving, analysis and communication. Teach students what they can’t learn easily online.
