I'm with you. Plenty of people (across all job industries, tech included) go out for long lunches and/or coffee and often aren't checking their notifications for most or all of that time. A nap is no different, and is just as, or more, important to productivity and health as food or coffee.
For certain kinds of "emergency response" jobs in tech, that may not be an option, but for everything else odds are your teammates can survive if you aren't available right that minute. And even emergency responders need shifts and breaks during shifts. If you're a developer, unless you're very actively training a new team member or something, I can't think of many scenarios where an immediate response is truly needed. This is HN and everyone has a counterexample for everything, so I'd be curious about other takes on this, but that's been my experience.
Remote-first companies seem to be very asynchronous (or at least try to be), out of necessity to accommodate people across all timezones, but also to encourage this kind of flexibility.
For certain kinds of "emergency response" jobs in tech, that may not be an option, but for everything else odds are your teammates can survive if you aren't available right that minute. And even emergency responders need shifts and breaks during shifts. If you're a developer, unless you're very actively training a new team member or something, I can't think of many scenarios where an immediate response is truly needed. This is HN and everyone has a counterexample for everything, so I'd be curious about other takes on this, but that's been my experience.
Remote-first companies seem to be very asynchronous (or at least try to be), out of necessity to accommodate people across all timezones, but also to encourage this kind of flexibility.