A Bestiary of Functions for Systems Designers
brunodias.dev
brunodias.dev
Like what are the different types of synchronous and asynchronous IO in Linux, Windows and BSD, and how do they compare and contrast.
A pretty interesting article though, even if it was completely different from what I was expecting.
Basically we are now at the point where a mathematician in a similar situation would dig out: empty set: {}, one: {{}}, two: {{},{}} ... ... yay - numbers, "now assume a spherical cow" and before you know it things get really weird.
IT isn't quite so clever but we do have some basic definitions and "systems" means: "systems" (####TODO: Fix recursive definition.) Systems can be designed and a Systems Designer might get involved in that activity. The more money that is paid to a vendor the bigger, better and more important the system - if Oracle is involved you will know this to be absolutely true. Games might be the focus of a system that is considered part of "systems."
A Games System Designer sounds like way too much fun to be involved in systems and so probably cannot exist.
Anyway, add Game to the title and we're all good. "Bestiary" is a nice touch but not quite good enough!