[DaveSchmindel]

Ah! But crontab.guru is such a beautiful UI/UX! I'd argue it offers the user everything it needs to perform what it needs to perform.

I will painfully admit I hassle with going from PT/PDT --> UTC more than I should, but after a while it was pretty easy to commit a simple number of hours (+7/8, depending on daylight savings timing) to memory.

I used to use [Hour](https://apps.apple.com/us/app/hour-world-clock/id569089415?m...) for MacOS to avoid this problem; I'm sure there's a similar or native solution for Windows & Linux as well.

[jrockway]

I know of someone that set their cron server to a weird time zone (not representative of the office or computer's physical location) so that when someone told them "it needs to run at 9:00", they could punch that into the crontab and the results would be ready before 9:00, even if there was maybe a transient error or something.

I am not recommending this.

[xyzzy_plugh]

The time between midnight UTC and 9 AM Pacific is a magical, horrible window during which billions of dollars of servers throughout the world heat up producing mundane reports.