Prelude: tmux For the rest of this post to make sense, you ought to have some understanding of tmux. tmux is a terminal multiplexer and session manager, meaning that if you disconnect from your machine you can reattach to your previous session and the state of your terminal tabs (managed within tmux) will be restored as if you had never left. It is a highly recommended tool for remote development. It is often considered a successor to screen.
Not to get too meta, I thought it would be appropriate to discuss my experience with Hugo in bringing up this blog. I generally followed the excellent quickstart documentation (which can also be very conveniently hosted locally). Overall, I like the tool but as can be expected it has some interesting features which I thought were worth pointing out. Shopping Around I did not do a tremendous amount of shopping around but I started with a few basic goals.
Several people have posited that the best coders are lazy, citing that they will write DRY (Don’t Repeat Yourself) code to make maintenance and testing easier and that they will use the right tools to solve their problems with the least amount of required effort. Well, the same principle applies when it comes to general productivity when it comes to working with computers, whether you’re a software developer, an Excel spelunker, or a human Markov chain email generator.