academyliner.blogg.se

1. #Once i learned to go mouseless im happier how to#
2. #Once i learned to go mouseless im happier install#
3. #Once i learned to go mouseless im happier update#

You can't learn all those keyboard shortcuts. You've heard about those mythical engineers that don't have to use the mouse at all. But the constant switch between mouse keyboard can be annoying and time consuming. To navigate around in your source code you probably use both your keyboard and your mouse. And since you are reading this, you are probably spending most of your time inside your IDE (which is Android Studio / IntelliJ).

#Once i learned to go mouseless im happier how to#

I agree, it might be frightening for many, but I tried my best to lower the fear.Īnd yes, the chapter 3 explains in details how to create an installer for the whole system.We spend most of our days in front of our computers.

#Once i learned to go mouseless im happier update#

Ubuntu was more problematic for me, because at each update my whole system was crashing, and I had no clue why. I barely spend time maintaining it (I update it every week, but it doesn't require much from me). I use it for 6 years myself and I never had any major problem.

#Once i learned to go mouseless im happier install#

Additionally I want to show that Arch Linux is not hard to install and it's a very stable system. Linux is on every server nowadays, I think it's super useful.įor developers to really understand what's going on (not copying blindly config from Internet) and therefore be able to customize their systems for their own needs. I wanted to write this book for three reasons:įor developers to understand new ways of working with text without switching between mouse and keyboard all the time.įor developers to understand a bit more the fundamentals of Linux-based systems.

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. The book's page if you want more information.Ī quick video explaining a bit the Mouseless Development Environment we build throughout the book. The cherry of the cake: you might learn two or three things about Linux-based systems, especially if you don't use the shell often.Ī sample of the book with the whole table of content. I've written this book to give away everything I know for your hands to stay on the keyboard when you work with plain text. It's like multitasking: it's tiring and ineffective. Why would you be interested by such a book? Switching your hands between the keyboard and the mouse takes cognitive energy. Its lengthy name: Building Your Mouseless Development Environment, powered by amazing tools like Arch Linux, i3, Zsh, the Almighty tmux of course, and Neovim. my first book is out for three weeks already! I'm so happy to write that, you have no idea. I didn't have any job, only the computer I was traveling with (Lenovo x220 for the win!) and some clothes. With difficulties and luck, I ended up with my girlfriend in a temporary place. I had to come back in Europe without any flat (I was subleasing it 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 due to my job, I began to travel in Asia in January 2020. 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 the Linux shell would be the most important tool, from an empty hard disk to a complete development environment? Would anybody like some guidance to build their first "Mouseless Development Environment"?