There are legitimate reasons to pull in someone after hours, but it really has to be catastrophic. I'd 100% want to be called in if I deployed something knocking out 911 service for a whole state and I was the only one with the knowledge to actually fix it in a timely manner. However, most problems are not like that and are either able to be delayed until an actual business day or can be solved by someone else.
Let's be real, we're talking about line of business apps and ecommerce stores making $5,000/day total revenue. "Critical infrastructure" has an entirely different failure model.
If the product that breaks in the night is SO important for the company, well, why is not the company paying for dedicated people (not the engineers who create the product) to take care of it when it's broken? As said above, while on-call you don't write code, you just turn off feature flags, reboot machines, etc.
If the company cannot afford that, then the product is not that important and can remain broken until the morning.
Even 24h fast food places hire 3 people (each working 8h)!
If you want things to not break, have redundancy in hardware and failover modes that let you function in reduced capacity.
Manual fixes should never be done in a hurry, and if your system is that fragile, I really wonder about the competency of your senior employees and leadership.
Clearly not, since you can have consciousness with only half a brain. Even a full hemispherectomy doesn't make you not conscious. In fact, there may be little change to the personality or cognition at all.
The symmetry between right and left brain doesn't really correspond to the types of symmetries they're talking about in the article. They're usually expressed as "The laws of physics are independent of X; you can substitute X with Y and the laws work the same." There isn't any kind of substitution here, so no place to apply the symmetry.
If some experimentator will destroy a half of his brain in such a way to not harm anything else - does he have a chance to keep being consciouness? That experiment kind of answers the question.
They used to say "tell me a little bit about yourself." At least for a literal-minded developer the "little bit" added some guard rails against unnecessary verbosity.
