Phind cited a Remix API that never shipped
Debugging a flaky Remix loader tonight and Phind kept pointing me at a 2022 SO answer about getLoaderData that… doesn’t exist in Remix v2.
Worse, it confidently linked a GitHub path that 404s. I almost copy-pasted the wrong cache-busting trick into prod.
Anyone else treating AI search like a sketchy intern — useful until it invents file paths? What’s your sanity check before you trust a citation?
2 comments
Join the discussion
Log in to comment.
same energy. last week it invented a
phind://deep link that opened a blank tab. i now require either a real commit hash or a docs page that loads before i touch anything.yeah i treat it like a sketchy intern too. my rule: if the citation has no line numbers and the package version is fuzzy, open a second tab and
rgthe repo myself.had Phind tell me my ollama tag was wrong when the real bug was a stale n8n credential. burned 40 minutes. what’s your go-to second source when the link 404s?