Yeah, that is pretty much what it does already: it tries to recognize test files and skip them. Dupehound is available for 12 languages Today.
Some languages like RUst you mentioned, have a clear tag that says "this is a test," but others do not, so the tool has to guess from file names and ends up missing some and skipping too much.
Also as I mentioned on the answer below, sometimes you actually do want to see the repeats inside tests, or normal code repeats on purpose too. So I am leaning toward letting users wave off one specific case by hand instead of skipping everything blindly.
What I use for: I use for identifying duplicated code. It is deterministic, doesn't use AI, offline, runs from CLI and is super fast (and free).
What I dislike: I won't say it I dislike, but it is not a tool that does all the jobs of a code review. For instance, it doesn't flag security issues. It is superfocused on code duplication (it performs better than Sonar for this use case) and is specifically useful for large codebases. Disclaimer: I am one of the collaborators, so take it with a grain of salt https://github.com/Rafaelpta/dupehound
agreed, but imo terminal and any conversational interface is not a silver bullet. Example: signup up for a ai assistant that lives in the email. Can't cancelled it bcs the founder assumed that since you ask anything in natural language every problem the user might have is solved. This is just pushing problems to users.
So true, just built a deterministic system to identify duplicated code. It's offline and doesn't use AI on purpose, since a gate that blocks your CI has to give the exact same answer every time, and finding dupes means comparing every function against every other (that's index work). It does NOT use AI. But ironically, I used AI to build it (https://github.com/Rafaelpta/dupehound )
This article misses the point. It is not about AI replacing workers, but about AI bringing more ROI. Can an AI convert twice as many customers as a $4k salesperson? It is reasonable to say that in a B2C setting, YES. I've seen that. Better SLA, fast responses during weekends, better adherence to existing playbooks, mapping out objections that are not in the playbook, and suggesting updates for the same prompt. In one week, the playbook evolved, and today we are converting more customers than the sales team. Does it capture the value of the $4k usd sales person ? If the ROI is superior, yes. Will I pay for it? That is a different story (we developed this ourselves).
You’re right. I’ve just changed the title of the article adding “(un)” to the beginning. I can’t prove the errors are intentional, but given the author’s reputation it would surprise me if they weren’t.
I sometimes feel guilty. I’ve tried to set goals (I really have) but it’s just not how I’m wired. I tend to improvise my way through things. Even as a kid, I remember never feeling that urge to "win" at anything. Sports, board games, whatever. Other kids would light up with competition. I’d just… show up, participate, drift through it. I always felt slightly out of sync with that whole dynamic. That’s why this line hit me so hard: “Some of the most powerful forms of progress emerge from people who stopped trying to win and started building new game boards entirely.” Maybe that’s been the point all along. Thanks for sharing this.
I miss Rushmore’s plain approach. Just enough quirk, sharp acting, and visuals that back the plot instead of hogging it. Newer Anderson films look like photo shoots: pretty, but the story drags. Same story dev teams hit when designers chase pixel-perfect screens and users still wait on real features.
ChatGPT ≠ Google-scale.Google: ~14 B searches/day; ChatGPT: ~37 M (~1 : 400). Only ~15 % of ChatGPT prompts look like classic “search”; most are writing/code tasks. Google’s own search volume grew 22 % in 2024 and still holds >90 % share. An LLM citation is nice for credibility, but it won’t move traffic or revenue anytime soon.
Never wondered why 14. But makes perfect sense. Early Unix feels like a masterclass in minimalism under constraint. Also fun detail: Unix V3 had 8-character limits before DOS made it famous.
[email protected]