Why invest your time in learning Tmux?

Modern development on POSIX compatible operating systems revolves around small command line tools that excel at one or two tasks.

Much of the power of the UNIX operating system comes from a style of program design that makes programs easy to use and, more important, easy to combine with other programs. This style has been called the use of software tools, and depends more on how the programs fit into the programming environment and how they can be used with other programs than on how they are designed internally. [...] This style was based on the use of tools: using programs separately or in combination to get a job done, rather than doing it by hand, by monolithic self-sufficient subsystems, or by special-purpose, one-time programs. Brian Kernighan and Rob Pike via Wikipedia

Tmux is built around this philosophy providing a lightweight container (or terminal multiplexer) to manage many consoles and hence many "special-purpose, one-time programs". Episode 1 gives a less-than-five-minute overview of Tmux.

I have been using terminal multiplexers for many years in my day-to-day software development and this series is a cumulation of what I have learned thus far. I sincerely hope that you are able to increase your productivity by following them. If you find them of value please share with other developers. — Best, Minimul.