I know not to hope for it to ever catch on, but my dream date-time format would be:
year/day/hectosecond.second(.millisecond and so on to the desired precision)
The current date-time, to the second, would be 2023/308/342.65
The days, like the years and second-based units, are 0-indexed.
There are 100 seconds in a hectosecond, and normally 864 hectoseconds in a day.
And to go with it, I'd advocate either a "3-on, 2-off", or "6-on, 4-off" work cycle, depending on the nature of the work, or even just personal preference. This way, today(308) would obviously be on a "weekend" either way.
year/day/hectosecond.second(.millisecond and so on to the desired precision)
The current date-time, to the second, would be 2023/308/342.65
The days, like the years and second-based units, are 0-indexed.
There are 100 seconds in a hectosecond, and normally 864 hectoseconds in a day.
And to go with it, I'd advocate either a "3-on, 2-off", or "6-on, 4-off" work cycle, depending on the nature of the work, or even just personal preference. This way, today(308) would obviously be on a "weekend" either way.