Yes shift the opening and closing times of everything. Get everyone to coordinate, so that your kids' school time doesn't shift relative to when you need to be at work, not to mention everything else where two different organizations have to do something that regularly happens at a particular time. Give up eliding this whole problem so that some programmers have an easier time scheduling backups or database compaction.
In fact, as some have suggested, we should also give up time zones and just use UTC for everything. That way when you have to schedule a Zoom call a few thousand miles away, there is no confusion as to the time. Some idiot might retort that since people like to sleep when it's dark, that instead of looking up the time zone difference, you'd have to look up what time the sun rises where they live.
I say screw them. Half of the world should just learn to live with sleeping during the "day" and go to work at "night." We've got electric lights now. It's a small price to pay so that programmers don't have to do time zone conversions.
If we're talking about radical time-related ideas, mine is to shift midnight to be the current 4AM. The reasoning is that many events last until past midnight, while 4AM is more or less the time when both the party and the work people are asleep.
If you want to get even more radical, abolish standardized time entirely and just have everybody maintain a personal calendar that reflects the times they are awake, when they are busy, and when they're available. The proliferation of electronic devices gets us halfway there already, eg. iPhones have sleep/wake hours that tie into alarms and do-not-disturb, Google Calendar lets you set working hours, etc.
Way back in my pre-parent days, I used to wake up around noon, roll into work between 1-2 PM, work until around 10 PM, and then go to bed around 4:00 AM. There was briefly a proposal to give me and a few other late-rising coworkers rollback privileges to the Google Maps codebase, because between the Maps team in Zurich, the Maps team in Sydney, the Maps team in NYC, and a few night-owls in California, that would give them 24 hour coverage with significant overlap for handoffs. It went nowhere because we didn't work on Google Maps and some VP probably balked at having people not in their org with full owners privileges, but it's an interesting example of combining timezones + personal schedules to get better time coverage.
While we're at it. I'd like for 9am to be 5pm, and for 12 to be 4:20.
oh please, 9am should be whenever I log into my work computer.
also obviously remove support for 12hour clocks from everything, who the duck thought having two different 4 O'Clock times every day makes sense. And what the insanity is the nonsense that write 12 mean 0 a.m. I.e. going from 11:59am goes to 12pm, like seriously who thought clocks braking basic math is a good ideaf!?!? Like the rang [11:59am;12am] is 12 hour and 1 minute wide instead of just 1 minute even through it uses the same unit.
Whilst we're at it, let's have 100 seconds per minute and 100 minutes per hour. I'm not sure whether I'd prefer 10 or 100 hours per day, though maybe 10 hours would be sufficient.
20 hours per day, 10 in the morning and 10 in the afternoon
I say keep the 12 hour clock, it is too ingrained, instead let's have twice as many days. April 42nd anyone?
Mine is to indicate time of day by what longitude the sun is at meridian.
> In fact, as some have suggested, we should also give up time zones and just use UTC for everything.
Obligatory link to 2015's "So You Want To Abolish Time Zones":
* https://qntm.org/abolish
* https://news.ycombinator.com/item?id=39692011
* https://news.ycombinator.com/item?id=26416337
* https://news.ycombinator.com/item?id=8902765
> Get everyone to coordinate
Lol. Lmao, even.
No further comment needed.