Don't forget changing the day 1/3 of the time. But more importantly, if I'm scrambling to solve an incident, the last thing I want to do is deal with time conversions in my head.

You just do it once and think in UTC going forward. But as I said to the other person, if you're only dealing with one timezone it's fine, just when you have multiple it's a lot easier to just deal with one time and let everyone convert.

I'd expect everyone who works in computer related jobs to know their UTC offset.

I'm able to subtract 8, but if I'm scanning logs it's one more thing to process.

If it's local time I know instantly when something happened, without having to do mental math.

Is there anything wrong with ISO8601 (including timezone offset) for storing times? They're in my local time, but they can be accurately converted to any other timezone.

No problem as long as it's all local, but it's a big annoyance to the other teams if I'm trying to coordinate with the West US team who're on PT, the East coast on ET, Europe on CET, India on IST, Australia on BBQ...

It's just easier for everyone if we agree on UTC and everyone knows their own offset.