4 ms·
The headline doesn't accurately represent the content of the blog post. It should be "GitHub's New Code Search is Bad for Finding __New__ Code". GitHub's new c
by hobofan 3y ago
The headline doesn't accurately represent the content of the blog post.
It should be "GitHub's New Code Search is Bad for Finding __New__ Code". GitHub's new code search is great at finding code (a vast improvement over the old one), and as it is optimized for finding code independent of temporal aspects, it's not good at finding _new_ code.
Sounds like a good tradeoff to me, as there conceptually aren't any reliable/unambigous indicators of "when" attached to a piece of code (same as for authorship). Should it count when the commit was authored? Should it count when the commit was pushed to GitHub? Should it count when the commit was merged to the default branch of the repo?