3 ms·

Do I read the manual of every tool I use before counting on it? Yes, absolutely. The first sentence of ripgrep's man page's description section is: ripgrep (

Do I read the manual of every tool I use before counting on it? Yes, absolutely. The first sentence of ripgrep's man page's description section is: ripgrep (rg) recursively searches the current directory for a regex pattern. By default, ripgrep will respect your .gitignore and automatically skip hidden files/directories and binary files. You cannot pick up a tool, start using it without understanding what it does, then tell the tool that it's doing things wrong.

godelski 2y ago
> Do I read the manual of every tool I use before counting on it? Yes, absolutely. Sorry I'm not sure I believe you and even if you are that rare case, I think you know most people don't. I'm a manual lover myself but haven't read all the manuals of all the tools I use. That would be extremely cumbersome given the sheer amount and the complexity of some tools. > You cannot pick up a tool, start using it without understanding what it does I don't disagree with the exact words but I do with what I think you're arguing. Lots of tools have a natural design where you can intuit their usage. A hammer or screwdriver is a great example. Many videogames also teach you how to play via level design without the need for tutorials (there's also many many terrible examples from video games and many sub par ones too). And that's what I'm arguing about when I'm talking about the direction of error. There's a natural signal coming back to the user so they know if something is wrong or isn't. But letting users think things are good when they aren't is an extremely costly error.