My absolute favorite is Betrayal at the House on the Hill.

It’s just designed so well. The pre-haunt phase allows new players to learn the basic rules of the game by playing. Like, we were playing this, and a somewhat seasoned member of the boardgame crew was late and she missed the base rules. We just shoved her a character, she was confused how no one explained her stuff, but after 1-2 turns of other people, she understood 90% of the base rules without explanation. That’s really impressive from a design standpoint.

And then, the game flips into the post-haunt phase, and some antagonist scenario happens. This is when things go nuts. One game, one player turned into Doctor Frankenstein, and Frankensteins Monster was placed on the board. And we as the normal players had to scramble to kill it. In another game, I turned into a giant snake god to kill everyone - but a bad cellar layout saved the players.

In other cases, there is a hidden, randomly chosen antagonist and things go nuts. People steal items from each other, because of good ideas and things go nuts.

I love this game. It starts out as a really approachable coop-game if you know action-point-based games. You bumble around in a haunted mansion, Bob usually almost dies because of bad luck (and we make fun of him), and then the haunt hits and it becomes everyone against Bob, except Bob is a horrible monster now.

No matter if you win or lose, you will have a funny story to tell how Bob is a jerk, or we were heroic.

To me, it feels similar to what’s happening on the server side. Server Side, most application handling got replaced with containers, because the dependency management becomes untenable if you’re pushing around just a couple of in-house applications. Here you use the distribution to offer a stable platform (container engine, monitoring, storage and such) and then run container on top.

And I think the desktop is on a similar journey for similar reasons, at least for faster moving or more complex applications.