3 ms·

SOMEONE didn't read the article > You code and you have the AI check your work. Treat it like a reviewer. That’s my advice in a sentence. Bro you're giving th

• andai 2mo ago
  >Preferably, don’t give the AI access to the codebase. Copy-paste snippets of your code in the web interface. Well, I can't ask it for an overview of a system it can't see.
  • qayxc 2mo ago
    > Preferably, don’t give the AI access to the codebase. [...] If the AI does have access to the codebase, this access is read-only. also > I don’t follow all these religiously. So if you need an overview of a system, you can and should provide access to the entire codebase. Even the rule itself says "preferably", not "don't ever". If you have different needs, you can always just look at it as a useful guideline. It's just a blog post by some rando on the internet, not the epiphany of AI coding's Ten Commandments.
• ithkuil 2mo ago
  Using AI to review our own comments before posting could be a good idea
• lubujackson 2mo ago
  Quite different advice, actually. I do not trust an LLM to review or to code by itself, but it can enlighten or expose blindspots, without requiring me to dig through the codebase, especially around unrelated downstream impacts. The point is to use LLMs as a research and concept navigation tool rather than a reviewer or "decider". Broad asks like "is this code good" are vague and lossy, narrow asks allow much less room for unknown unknowns.