Title: Discussion 5 — One Hyperparameter to Rule Them All?
Course: AIINFRA 301: Production RAG & LLMOps — Observability and Evaluation > Section: Week 05 — Chunking Strategies for Real-World Documents

💬 Discussion 5 — One Hyperparameter to Rule Them All? (20 pts)

Imagine you're responsible for chunking two very different corpora: a set of formal legal contracts, and an export of casual Slack messages from a team channel. Post a response addressing:

- Would you expect the same chunk size and overlap values to work well for both corpora? Why or why not?
- What structural differences between legal contracts and Slack messages would push you toward different chunk sizes, different splitters, or even different strategies entirely (fixed-size vs. recursive vs. semantic)?
- What does your answer tell you about treating chunk size as a single universal hyperparameter you tune once and reuse everywhere?

Then respond to at least two classmates: challenge or build on their reasoning, and where possible, point to a specific structural feature (e.g., contract clause numbering, Slack thread replies) that they didn't mention.