When folks ask me a question about our codebase internally I try to a) answer the question b) say "If I were trying to find the answer to that question with our tools, here's my entry point, here's the search query, and here's my mental heuristic for why I'd click on result #3"
-
Show this thread
-
This is trying to thread the needle on always, always being happy to give responsive answers to questions while also increasing people's ability to self-serve on them in the future.
2 replies 3 retweets 37 likesShow this thread -
Since it's publicly available, let me mention that the most common tool I use for answering these questions is livegrep and that I intend to boot up a livegrep instance on the first day of every startup for the rest of my life. It borders on miraculous.https://github.com/livegrep/livegrep …
3 replies 13 retweets 151 likesShow this thread -
"What's livegrep do?" Instantly grep all code at your company from a web interface, with it producing the relevant files, contextual snippets, and links to the full version in Github/GHE/etc. It's blaaaaaazing fast, too, even across our Very Materially Sized codebase.
3 replies 6 retweets 53 likesShow this thread -
I'm not familiar with Hound so I can't answer that question usefully, but you can play with an instance that searches the Linux codebase at https://livegrep.com
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.