I rewatched The IT Crowd over a few evenings this month, the way you do when you are too tired to start anything new and the remote is closer than the bookshelf. I expected to laugh at "have you tried turning it off and on again" and go to bed. Instead I sat there feeling oddly seen, and then slightly attacked, because under the broad comedy it gets a surprising amount uncomfortably right.
the basement is real
The thing it nails first is the geography. Roy and Moss live in a basement, lit like a server room, ignored by everyone upstairs until something breaks. That is not a joke, that is a documentary. I have worked in offices where the engineering team was physically the furthest from the people making the decisions, down a corridor, behind a door that needed a card nobody upstairs had ever been issued. The distance was not an accident. It is hard to ask someone to do the impossible by Friday if you have to look at them while you do it.
The show turns this into farce, but the underlying truth is that IT has historically been treated as a cost centre that occasionally emits people. You are visible when the email is down and invisible the rest of the time. The whole "did you see that ludicrous display last night" running gag, where Roy and Moss desperately try to pass as normal sociable humans, is funny because the gap is real. You spend your day reasoning about machines and then someone asks you about the football and your brain returns a null pointer.
the calls
What it gets most right is the support call. The bit where Roy answers the phone, says "have you tried turning it off and on again", and then "is it definitely plugged in", is treated as a punchline. It is not a punchline. It is the correct first two diagnostic steps and it resolves a genuinely enormous fraction of incidents. The joke lands because every engineer in the audience knows it is true and slightly resents that it is true.
There is a deeper accuracy in how the callers behave. Nobody describes the actual problem. They describe their feelings about the problem, or the last thing they touched, or a theory they have invented that is confidently wrong. The skill the show quietly portrays, under the slapstick, is translation: taking "the internet is broken" and working back to "your monitor was switched off". That translation layer is most of the job and almost none of the recognition.
There is a kindness in it too, which the show occasionally lets through under the cruelty. Roy is rude to callers, but he keeps answering. The job, done properly, is patience as a service: explaining the same thing in three different ways until one of them lands, and never letting on that you explained it yesterday to someone else. Comedy needs the exasperation to be loud. In real life the exasperation stays internal and the voice stays level, which is its own small daily act of professionalism that nobody ever sees.
the part that stings
The episode that aged into something sharper for me is the one where they invent "The Internet", a small black box with a blinking light, and hand it to the rest of the company as if it were the literal internet. Everyone believes them. It gets paraded on stage. The joke is that the business has no idea what any of the technology actually is, and will accept any confident explanation delivered by someone in a lanyard.
I have lived a gentler version of that more times than I would like. The gap between what a system actually does and what the people relying on it believe it does is enormous, and it is filled, on a good day, with patient explanation, and on a bad day, with a metaphorical black box with a blinking light because the truth would take an hour and a whiteboard. The show plays it for laughs. In practice it is the thing that erodes you, slowly, over a career: being responsible for something nobody around you can see.
what every show gets wrong
Here is the one thing none of them get right, The IT Crowd included, and Silicon Valley and the rest along with it. They all compress time. A problem appears, there is a panic, and it is resolved within the episode, usually in a single heroic burst. Real incidents are not like that. The genuinely bad ones are slow. They start as a faint wrongness in a graph that you ignore, become a nagging worry over a quiet afternoon, and only later turn into the thing that owns your weekend. The drama is not the shouting. It is the three hours of reading logs in silence, the false lead you chase for forty minutes, the fix that is one line and obvious in hindsight and invisible at the time.
That slow, undramatic texture is the actual lived experience of working in IT, and it is exactly the part that cannot be filmed, because watching someone read a log file is not entertainment. So the shows give us the basement, the support calls and the institutional blindness, all of which they get right, and then they hand us a resolution in twenty-two minutes, which they always get wrong.
I do not hold it against them. If they filmed the real thing it would be unwatchable, and I would still be at work. But it is funny which parts land. The comedy I expected to find dated is the comedy that holds up, because the social shape of the job has barely changed in fifteen years. The basement moved to a Slack channel and the card-locked door became a VPN, but the distance is exactly the same. I finished the rewatch genuinely fond of it, and then I checked my phone out of habit to see if anything was on fire. Old reflexes. The show would have approved.