Two Hundred Fifty Things
a Game Designer Should Know

In 2018, architecture critic Michael Sorkin wrote "Two Hundred Fifty Things an Architect Should Know". The items on the listicle are poetic, thought provoking, introspective, practical, and sometimes even canonical. They all connect architecture with broader social issues.

In July 2020, four months after Sorkin's death due to COVID-19, I challenged my Twitter friends and aquaintances to come up with a similar list for the discipline of game design. I collected my favorite submissions here, roughly in the order they were suggested, with some minor edits and links to the authors' profiles.
The full thread includes many more that didn't make the cut for various, mostly formal, reasons. Feel free to keep adding your things.