Team vim, team emacs, or team โmy editor doesnโt start warsโ? One line, no essays. Go!
Any conversation
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
WezTerm for local and remote multiplexing really is the ideal experience - it's so much better than using zellij, tmux, zmx, and friends.. I don't think they pitch this feature hard enough on their site.
I think the in-terminal multiplexers have their place - e.g. if you need to access from mobile (no WezTerm there) or on machines where you simply don't want to install WezTerm for some reason. WezTermrm could probably eliminate that last one by packaging just the mux server.
setting up some of my workflows based on this writeup - ludwigabap.com/โฆ/on-my-personal-โฆof-the-tools-i-use/
Particularly a big fan of zellij amongst others
Also venturing into having agents enable more of my work - let us see how that goes.
