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.