A town-clerk intern copies the same headers, retry loop, and messag…

Question

A town-clerk intern copies the same headers, retry loop, and message assembly into every feature branch for chatbot, summarizer, and extractor work. What should a reviewer ask for instead?

Accepted Answer

Wrap the LLM behind one shared client or chain so those features reuse retries and the template store. Scattered HTTP copies will drift. — The same headers, retry loop, and message assembly should live in one shared LLM client. Copying that HTTP block into every feature branch guarantees drift. A raw socket per feature, or a serving stack per feature, does not fix the shared-call problem.

Answer

Keep copying the HTTP block so each branch can invent its own timeout and preamble.

Answer

Drop the shared client and paste a new raw socket open into every feature.

Answer

Give each feature its own model repository and a separate serving stack before anyone shares a template.

A town-clerk intern copies the same headers, retry loop, and message assembly into every feature branch for chatbot, summarizer, and extractor work. What should a reviewer ask for instead?

Short Explanation

Full Explanation