3 ms·
In my experience it's great for: 1. When your code is too big for your IDE's built in global search. 2. When you want to share searches with others. #2 is gr
by gravypod 4y ago
In my experience it's great for:
1. When your code is too big for your IDE's built in global search.
2. When you want to share searches with others.
#2 is great for design docs. You can say "<link> shows the bug is common in API usages" or "<link> shows x% of our files do this"
Edit 3. When something does go wrong.
> If I need to replace or find something across all repos in my organisation, or god forbid, Github, then something went extremely wrong architecturally.
If your plan B for messing something up is to not have a plan B you're going to have a bad time when plan A fails :)
Unfortunately, hope is not a strategy.