5/21/2023 0 Comments Mouseless development environment![]() Nevertheless, I had things to do and deadlines to meet, so I continued typing… Keyboards (down the rabbit hole we go) □Īround 6 months ago, I was sat at my desk when I noticed a slight pain in my hands, I wasn’t quite sure what the pain was or how I had caused it.Equip yourself with the best text editor Spacemacs (vim meets emacs).Try to strengthen your fingers and forearms e.g.Stretch your forearms, fingers, etc multiple times throughout the day,.So that you can learn the vim keybindings and get the most out of them,.This has definitely been the hardest injury that I have ever had to deal with, so I hope the info in this post can make the process easier for anyone in a similar situation.įor those in a rush, here’s a quick summary of the tips I would give to a fellow RSI sufferer: I’ve decided to start the post with my story and then afterwards go into detail about what I consider the most import aspects of my recovery (or management). My RSI affects my fingers, hands, wrists and forearms so it has had a pretty significant impact on my day-to-day life, which I normally spend programming in python or writing in LaTeX. I’d been putting it off because the amount of content that I wanted to include seemed to be increasing exponentially with time.Īnyhow, I’ve decided to go for it and I’m hopeful that I’ve selected the most important parts of my recovery, especially for a fellow programmer. Then, they can change their systems as much as they want after they acquired the necessary knowledge.I’ve wanted to write a blog post about my journey with repetitive strain injury (RSI) for quite a while now. I thought that publishing an e-book would be a good compromise: I can still update it from time to time for free, I have a coherent whole, I could add as much explanations for the readers to understand what they're doing, by building something precise. I guess it's because CLIs are mature tools which don't need many new functionalities due to their "composable" nature. I knew as well that these technologies don't evolve very fast I use them for 6 years now, and I barely changed my custom install of my system during that time. If I describe the same thing in the context of any Linux distribution, I lost the benefits I just described. It's what I did, and it's easier for the readers because it's more focus, I can be more descriptive, and I get rid of a whole class of errors. A chapter of the book doesn't make sense by itself, except if I make it more general.įor example, I could explain how to use and configure tmux in the context of Arch Linux. I thought about writing blog articles, but I also wanted something coherent and presented as a whole for the readers to build everything from start to finish. I hesitated to write a book about it, because of the reasons you mention. If you want to know why, I wrote a bit about it.Īny feedback, positive or negative, is always welcome :) The "behind the scenes": what tools I used to write this book.If you don't want to watch everything, you can jump to the chapter you want. A quick video explaining a bit the Mouseless Development Environment we build throughout the book. ![]() ![]()
0 Comments
Leave a Reply. |