After reading the article I didn’t pick up what any of the advantages are of 28hr days other than being able to communicate with other regions of the world on certain days. I suppose that could be a very important factor for some people who do work in a geographically dispersed area. A few things I would be concerned with are: 1) your SO is not on the same schedule and really for what isn’t a solid reason. I could se…
Showing my age here but...
I and some of my friends/classmates used to do the 6day 28hr cycle, to ensure we had access to the computer lab where "normal people" were asleep during the week, but were still mostly "in phase" with everybody else on weekends for socialising.
For those of you who don't understand the term "computer lab", those were the days where my Comp Sci class involved writing/running Pascal code on a shared VAX-11/780 which (from memory here) shared 64MB of memory across all users of the 100 or so terminals attached to it. During the day, especially close to assignment deadlines, there were often long wait times to get one of the terminals. If you were there (and awake) at 10pm or 4am, there was usually only a handful of other people using it, with no waiting queues and with noticeably faster performance.
(When I started 2nd year, the first year class behind me still learned Pascal, but got to use the new Macintosh lab. That kinda made the 28hr phase shifting unnecessary, but a bunch of us persisted anyway. By 3rd year, the VAX was under-utilised enough that they added a bunch of modems, and I could connect from home via a 1200/75 baud modem from the Osbourne1 Z80/CPM machine I had at home.)