When I started as an IT dogs-body I was lucky enough to do quite a bit of travelling. For a young guy this was awesome; configure Exchange servers, see the world! But it also meant I was hopelessly naive AND due to my extreme Britishness I didn’t speak any other languages (even English was ropy).
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).
I’ve been lucky enough to do quite a bit of travelling throughout my working life. Most of the time it wasn’t particularly glamorous (“Be an IT guy! See the inside of server rooms in exotic locations!”) but occasionally I’d get to do something particularly cool.
Like being driven to the centre of New York City in a chauffeur in an enormous stretch limousine.