Basic code searching skills seems like something new developers are never explicitly taught, but which is an absolutely crucial skill to build early on.<p>I guess the knowledge progression I would recommend would look something kind this:<p>- Learning about Ctrl+F, which works basically everywhere.<p>- Transitioning to ripgrep <a href="https://github.com/BurntSushi/ripgrep">https://github.com/BurntSushi/ripgrep</a> - I wouldn't even call this optional, it's truly an incredible and very discoverable tool. Requires keeping a terminal open, but that's a good thing for a newbie!<p>- Optional, but highly recommended: Learning one of the powerhouse command line editors. Teenage me recommended Emacs; current me recommends vanilla vim, purely because some flavor of it is installed almost everywhere. This is so that you can grep around and edit in the same window.<p>- In the same vein, moving <i>back</i> from ripgrep and learning about good old fashioned grep, with a few flags rg uses by default: `grep -r` for recursive search, `grep -ri` for case insensitive recursive search, and `grep -ril` for case insensitive recursive "just show me which files this string is found in" search. Some others too, season to taste.<p>- Finally hitting the wall with what ripgrep can do for you and switching to an actual indexed, dedicated code search tool.