![]() The color does not demand his attention, the soundless machine doesnt interrupt him. Thats why Torvalds famously painted his walls pastel green and is very anal on having a soundless machine. This gives me more time to focus on the actual code and lets me concentrate through longer periods of time on said code. For me, keybindings do the same because Im faster and perform mechanical/mindless actions to move around the code/PC. So thinks like working with less interruptions or quiet places lead exactly to that, less mental context switches. This is not ideal since depending on your work and how complex ur code is, you may find it hard to place urself again mentally at where you were when you were thinking of item A, PRIOR to the context switch. That sometimes, again in my experience, leads me to more context switches.Ĭontext switches are when our brain is thinking about item A and then, for some reason, goes and thinks about item B (switches). Less thinking on keybindings/mouse clicks = more time thinking on code.įinally, the big one is, sometimes dragging ur mouse across the screen even though may seem fast and harmless requires, for me at least, a tiny bit of concentration and time to aim. Keybindings, when muscle learned do not require any thinking after some time. The central idea of these tools is to REDUCE COGNITIVE LOAD and/or REDUCE THE NUMBER OF CONTEXT SWITCHES during work. The effectivity is not due to the actual speed of typing in a keybinding in comparison to a mouse click. The same way keybinds in vim are effective once the muscle memory is there, so are keybindings to change desktops/show-windows/change-tabs/launch-apps and so on. The thing about mouseless development is not about being cool or just doing it for doing it sake of doing it. If you want to know why, I wrote a bit about it. The "behind the scenes": what tools I used to write this book.A sample of the book with the entire table of content.A quick video explaining a bit the Mouseless Development Environment we build throughout the book.Long story short, you can now look at the result: They even helped me proofreading it (I'm not a native English speaker, as you can see). ![]() They helped me a lot and provided the motivation to keep going. I shared with them, during the 8 months of intense writing, the process, the doubts, and the ideas I had for the book. I wasn't alone: I had the support of my family, my friends, my girlfriend, and the amazing subscribers of my newsletter. Its lengthy name: Building Your Mouseless Development Environment, powered by amazing tools like Arch Linux, i3, Zsh, tmux, and, of course, the Almighty Neovim. It took me 24 years, but it doesn't matter: I made it! I'm so happy to write that, you have no idea. Without any job but a lot of time, equipped with the computer I was traveling with (Lenovo x220 for the win!), I thought: that's the moment. With difficulties and luck, I ended up with my girlfriend in a temporary one. ![]() ![]() I had to come back in Berlin without any flat (I was subleasing it to other people for 6 months). But I was working full time and I also knew I wanted to travel, so I put the project on hold.Īfter some good old burnout, I began to travel in Asia in January 2020. I began to poke around and I realized that, indeed, many were interested by the idea. One and a half year ago, I was wondering: would anybody be interested by a book describing how to build a system where you could use the shell very easily, from an empty hard disk to a complete development environment? Would anybody like some guidance to build their first "Mouseless Development Environment"? ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |