Ai Coding And Product Systems medium
Your answer engine has a fixed latency budget of about 3 seconds and a per-query cost cap. Answers are fluent but often wrong because the supporting sources are weak or off-topic. Where should the budget go?
- A Move more of the budget into generation with a larger model, since better reasoning can compensate for weak or partially relevant sources.
- B Cut retrieval to the top 3 search results to free latency for longer, more detailed generated answers with richer explanations.
- C Spend more on retrieval: fetch 10-30 results, rerank passages, and let a modest model synthesize from the best evidence.
- D Skip live search and answer from the model's parametric knowledge, citing sources afterward by searching for pages that match the text.
Answer: C. Spend more on retrieval: fetch 10-30 results, rerank passages, and let a modest model synthesize from the best evidence.
An answer engine's quality is bounded by its evidence, so it spends its budget on **retrieval and reranking** and accepts a modest generator. A larger model (A) is tempting, but it still cannot cite facts it was never given, so it produces more confident errors. Post-hoc citation (D) produces sources that only appear to support the answer. Putting the budget into generation makes sense for reasoning or creative tasks that do not depend on fresh facts.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Your assistant uses a classifier to route queries to a small or large model, which saves 60% of GPU spend. Analysis shows about 20% of hard queries are misrouted to the small model, which then gives confident wrong answers, and regenerate clicks on those threads have doubled. What should you do?
- Your workspace AI retrieves the top-k chunks from a shared vector index and passes them to the model with ACL metadata and a system prompt saying 'only use documents this user can access.' A user just received an answer quoting a private HR page they cannot open. What is the correct fix?
- Your support bot answers billing questions. One user has asked the same refund question three times, and retrieval confidence for that topic is low. What should the bot do next?
- Your AI review system receives a 4,000-line pull request spanning 60 files. Sending the whole diff in one prompt yields shallow, generic comments, and real bugs in files near the middle of the diff are missed. How should you structure the review?
- In your ChatGPT-style assistant, power users keep single threads running for weeks, reaching about 150K tokens. Cost per turn keeps climbing, latency is rising, and the model increasingly misses facts from early in the thread. What should you do?
- Your workspace AI filters retrieval using ACLs stored in the vector index, which is rebuilt nightly. An admin removes an employee from a confidential project page, but for the rest of the day the employee can still get AI answers drawn from it. What is the right fix?