I’ve started running a D&D campaign using the Fantasy Grounds software with my friends. After a few quick mini-adventures to get used to the system, we’re going to launch into the Out of the Abyss campaign.
Normally a spoiler warning would be appropriate in case you want to play this yourself in the future but the likelihood of my players;
Giants: Citizen Kabuto was a favourite at our LAN parties for a long time. It’s an interesting game; predominantly a single-player game it had a rudimentary multiplayer tacked-on, seemingly as an afterthought.
That meant multiplayer was a massive sand-box to play in with very little thought to balance.
Upset customers, complex systems, poor documentation, high-pressure situations, bizarre legacy choices. Working in IT is hard work.
Except when it’s not.
Watching installations / patches run, interminable meetings, deciphering manuals (“What does ‘Klaatu barada nikto’ mean?”), hanging around for a change window to open; there can be plenty of waiting around.
IT projects past a certain size get quite complex. They have a lot of moving parts and often those parts have to be aligned correctly and at the right time to make everything work. In turn, that means you need the various people to pull together to make sure the project as a whole delivers. Sometimes the team doesn’t succeed but normally everyone is pulling in the same direction. There is no “I” in team! Etc Etc
There are exceptions. In one place I worked the IT departments were actively trying to push each other under a bus. Think ‘Game Of Thrones’ with RAID arrays.
In the IT department where I first worked, there was a Network Admin who was a bit ‘highly strung’. He’d get quite short when things got tense and he liked things done the way things were always done (he supported the physical network and Novell; this was in the time when Microsoft NT was just starting to make inroads into business).