Re:Mise-en-place for knowledge workers
by reddit_clone on Friday July 02, 2021 @06:39PM
(#27717765)
Yes! I started a very similar process just this week.
Some of us have no choice but to multitask. I just learned about multiple desktops in Mac OS X and using something very similar to what you just described.
Each desktop gets its own browser window, emacs frame, Iterm window and a sticky. Sticky says what was the last thing I did and what is next. So context switching is easier.
I keep Outlook and Slack on a second monitor always visible. So far I am liking it. I am dreading the inevitable reboot.
I also wish Apple supported renaming the virtual desktops.
Re:Mise-en-place for knowledge workers
by japanuspus on Saturday July 03, 2021 @12:57AM
(#27719456)
Same here. Tried a few times previously, but this time I took the time to set up proper keyboard shortcuts which made all the difference.
For windows, this project is a great way to get keyboard shortcuts for desktop switching: https://github.com/yalibian/i3-windows
I also have things set up so that there is a keystroke that raises the editor on the current desktop to the top. Another for the browser and another for the terminal. When I switch to another desktop, the same keystroke raises a different editor process for that desktop, etc. So within a desktop, I switch between these apps using the same keystrokes regardless of which desktop I am on. And there is only one way to switch desktop. I can't switch to another desktop via choosing another application on another desktop, because the other applications that are not on the current desktop are completely invisible.
When I'm working on something with a Scala backend, an Elm frontend, and C/C++ embedded device, and when I need to go back and forth often between these sub-applications making related changes, I can't afford to close and reopen each one when I change the language/repo. I can change desktops very often this way. eg. Add a new field to the frontend. Immediately add it to the backend and the embedded also. But they are in different repos. etc. etc.
If I have one editor opening all three projects it is a nightmare to navigate between files. But one editor for each language and repo is the sweet spot for me. And it means my documentation for Elm is all in a separate browser window from my documentation for Scala (which is on another desktop) etc etc.
Sorry this was so long, but I think all the details add up to making it an efficient system.