thanato0s

15 ms·

91.
by thanato0s 6y ago
I thought the same before trying to use my actual dev environment, but, at least for me, it felt more enjoyable to stop using the mouse when I was coding. I think the best is just to try both approach and see by yourself.
92.
by thanato0s 6y ago
The problem is not necessarily to be fast for me (I know people who are very fast with the combo mouse / keyboard) but more if you like it. If you don't enjoy working with your tools, you'll have a lot of friction to do your
93.
by thanato0s 6y ago
I agree with most of what you're saying. Now, about the skills of the users, I think people are smart and can learn more easily than we think, if and only if they're taught right. It's what I tried to do. I don't know if
94.
by thanato0s 6y ago
These tools take a lifetime to master, that's true; but I could code in Neovim in two weeks. I think if you decide seriously to learn it, you can be effective with it pretty fast. Easy to learn, hard to master. That's what I like,
95.
by thanato0s 6y ago
I didn't think about that, but now you speak about it I think it's true. Thanks for that, that's interesting.
96.
by thanato0s 6y ago
I don't hate the mouse, but I think staying on the keyboard when you work with text (like code) is way more comfy. The problem is not the mouse, it's always switching your hand between keyboard and mouse. Additionally, the system
97.
by thanato0s 6y ago
I would tend to agree with that, distros are not that different from one another in the grand scheme of things. But there are still differences; I speak about them at the beginning of the book. For Arch Linux, the three important ones are f
98.
by thanato0s 6y ago
Thanks! I hope you'll like it! If you have any question, feedback, or problem, don't hesitate to write me an email. It's on the page where I sell the book.
99.
by thanato0s 6y ago
Thanks for that. It's reassuring. I've always tried to do exactly that, and my readers were always thankful for this kind of direction, so... I continue :)
100.
by thanato0s 6y ago
Thanks! I had a newsletter, and my subscribers were super helpful. Seriously, without them, I wouldn't have finish the book. I thought about keeping the newsletter, but I already had one for my blog. So I simply asked them to switch fr
101.
by thanato0s 6y ago
I think that's true. It's always good to explore new ways, especially the ones you don't agree with. Even if you still disagree at the end, I'm sure you'll learn something. I tried Ubuntu a couple of months ago, as
102.
by thanato0s 6y ago
Change is part of life, isn't it? That was deep, I know :D Seriously, maybe I'll write in 10 years "I was wrong: just install Ubuntu and you'll be happy". It will be a very short book though... but it's good to
103.
by thanato0s 6y ago
I think it's good to be the devil's advocate. Different opinions are great to ask questions about our own. I don't have any number, that's true. But I know that I enjoy using this system way more than any other I tried
104.
by thanato0s 6y ago
If I simplify a bit, I see two different approaches: 1. You write something broad as you say. You present many options to the reader. The book is not practical anymore, because you don't speak about something in particular but some gen
105.
by thanato0s 6y ago
I used Pandoc for the PDF; the links don't work because it's a sample. They work in the real book. About selling myself short: you're probably right. I'm struggling with imposter syndrome, like many, so I've a tende
106.
by thanato0s 6y ago
"I don't want to try i3 or Vim. What's the point using less of the mouse? Such a waste of time!" That was me, 6 years ago. My colleagues were pushing me to try the tools they were already using for years. They are very g
107.
Show HN: I wrote an entire book to build a mouseless dev environment(themouseless.dev)
353 points by thanato0s 6y ago|217 comments
108.
Man pages for Arch Linux packages online(man.archlinux.org)
2 points by thanato0s 6y ago|0 comments
109.
Pair-programming tips and tricks for coaching a remote team(philippe.bourgau.net)
2 points by thanato0s 6y ago|0 comments
110.
by thanato0s 6y ago
Why we have so much crap is not necessarily because of developers. In my experience (10 years), it's almost never the case. 1. Bloated and useless functionalities. More functionalities will make any software more complex. If these func
111.
The Differences Between Interpreter and Compiler Explained(thevaluable.dev)
1 points by thanato0s 6y ago|0 comments
112.
How I Made $30k on My First Self-Published Book(randallkanna.medium.com)
2 points by thanato0s 6y ago|0 comments
113.
Google Interview Questions Deconstructed: The Knight’s Dialer(alexgolec.dev)
98 points by thanato0s 6y ago|121 comments
114.
by thanato0s 6y ago
I ended up watching the two videos from Sean Parent mentioned here and they are great! His explanations are simple but touch important considerations we should have about type, especially when we begin to create some ADT. Thanks a lot for t
115.
by thanato0s 6y ago
That's interesting... German has still the genitive case and it is formed with an "s" too. That's a nice resource, thanks for that!
116.
by thanato0s 6y ago
Nice! I didn't know indeed. Thanks for that!
117.
by thanato0s 6y ago
It is, and I fixed it yesterday. Of course I didn't push it... Thanks!
118.
Type Systems Explained with Examples(thevaluable.dev)
114 points by thanato0s 6y ago|31 comments
119.
Steve Yegge Posts (2015)(sam-koblenski.blogspot.com)
2 points by thanato0s 6y ago|0 comments
120.
How I Made the Internet Garbage(youtube.com)
1 points by thanato0s 6y ago|0 comments

More ›