...Badly enough. Anyway to sustain high loads when happen my mix is: - most of my digital life in Emacs/org-mode(org-attach,org-roam,ol-notmuch,...) so (almost

...Badly enough. Anyway to sustain high loads when happen my mix is: - most of my digital life in Emacs/org-mode(org-attach,org-roam,ol-notmuch,...) so (almost)anything is ready at my fingertips, I can have a clear view of anything case by case or build one on the fly with org-ql/zetteldesk etc all in an unique ecosystem, not many different places to look for anything; - noting most things, especially too offload relevant details and being able to see long/mean terms slow stuff normally not easy to spot and often a source of time waste if not spot in time; - extensively using email aliases to easy scoring messages, when I'm in a rush I can simply cherry peak mails by alias filtering instead of unread so when I can't do anything I just get exposed to what I can do in a good priority order, well, good as good I can draft it up front, here count notmuch, Emacs, MailDrop and a local-based mail setup; - reduced number of com channels: people must know that they can reach me ONLY physically, by classic phone (VoIP, few numbers with a small domestic pbx) or mail. No n-th chat apps, no third party modern suite (Meet, Teams, Zoom, WebEx etc); - anything that can be done quickly done ASAP with the old military adage "if it's a life-or-death urgent: ignore it, they are already dead; if is very urgent next: week might be good; if it's just a bit urgent: tomorrow it's ok; if it's NOT urgent: do it ASAP!!!" so I try to avoid piling up things to have the emptiest pipe possible when a peak arrive, that's the part that work less though...