Hi everyone,
Stjepan here from Manning Publications, posting with moderator permission.
We’ve just released Domain-Specific Small Language Models by Guglielmo Iozzia in print. I wanted to bring it here with a question that’s more useful than another “small models vs. large models” argument:
What evidence would convince you to ship a smaller, specialized model instead of calling a larger one?
Not just a good benchmark score. What would you need to see on your own workload: performance on rare cases, behavior outside the training distribution, latency under load, or the cost of maintaining the whole thing?
That’s the practical territory this book explores: adapting pretrained models to domain-specific tasks, parameter-efficient fine-tuning, quantization, and local deployment on modest hardware. It also covers integrating these models into RAG and agentic applications.
I’m posting on the publisher’s behalf, not presenting a new research result or claiming small models are always the right answer. I’d especially like to hear where specialization didn’t pay off. What looked promising in evaluation but fell apart once actual users got involved?
For anyone interested in the book, Manning is offering this community 50% off with code PBIOZZIA50RE.
Book page: https://www.manning.com/books/domain-specific-small-language-models
We’re also giving away five ebook copies, one each to five people who contribute most meaningfully to the discussion. We’ll select for useful technical detail, thoughtful questions, and lessons others can learn from—not upvote counts or praise for the book. Critical takes are welcome. No purchase needed.
If you’ve tried this, tell us about the task, the model, your hardware constraints, and the failure that mattered most. Did you keep the smaller model, move to a larger one, or decide you didn’t need an LLM at all?
Thank you.
Cheers,
Stjepan
Manning Publications