I'm trying to get back into an old favourite of mine: computer programmer simulator. This has been available on more or less any hardware right from the days when computers had year-long rows of valves ('tubes' for those on the other side of the pond), punch tape readers (one of which I found recently when clearing out my parents' loft), and a small oscilloscope screen that displayed a wiggly line that only the boffins of Bletchley Park could decipher. (Not that they'd tell you what it meant if they did. Or even admit to knowing where Bletchley Park was.)
The object of 'computer programmer simulator' is to pretend to be a computer programmer (doh!), which you do by typing instructions at random, in the hope that they will result in something happening. It rarely does, and instead you are presented with a long list of 'errors' and 'warnings' which you deal with by turning the lines which generate the errors into comments, and ignoring the warnings. This usually results in a program which consists entirely of comments, at which point the warnings will all have gone away, thereby proving that they weren't important. If you can create a program that actually compiles and runs without errors you have won the round, and get extra points if the program does anything. If it does anything interesting, you advance to the next level. And apparently, if you program actually does what you intended it to, you've won the game, though I've never managed to get that far.
I have it on good authority that this is the way real programmers work, though they tend to cheat by copying code from Stack Overflow, a website where people post the occasional bit of code they've managed to concoct that doesn't generate errors. This makes it a little easier to come up with programs that do something, at which point the object of the game is to persuade whoever is paying for it that whatever it does is actually what they wanted all along, even if they were asking for something else entirely.