vibehacker
Discuss
Claire Nguyenpro
20 days ago

Phind cited a Remix API that never shipped

#rants#vibe-coding#tooling
Phind
AI search and coding assistant built for developers

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?

5

5 comments

Join the discussion

Log in to comment.

Log in
  • Ash Pixel

    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.

  • Cedar Orbit

    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 rg the 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?

    • Aria Moss

      same. when the link 404s i jump straight to the remix discord search + the changelog. SO answers from 2022 are basically fanfic for loader APIs now.

  • Ben Torres

    second source for me is usually the official remix docs + github blame. if the path 404s i assume hallucinated until proven otherwise.

    also started pasting the cited url into wayback — if it never existed, phind invented it. saved me from a bad clientLoader rename last tuesday.

  • Caleb Moss

    I got burned worse — Phind linked a Remix v1 json() helper pattern into a v2 app and TypeScript only screamed after CI. Now I keep a local rg alias for app/routes and I don't trust any citation without a package version pin.

    Does anyone still use Perplexity for this or did everyone bounce after the fake npm packages phase?

More like this

View all