> Guide it a bit here and there like a tech lead and you get everything done

How do you validate and verify that outcome?

Or does Qwen-3.8-27B do the validation and verification for you as well? If so, how do you ensure that's correct?

You check its work and if it seems to do its job well enough most of the time, you just start to trust it.

Personally Qwen3.8-27b has not proven itself to me for the projects I’ve tried to use it for. It doesn’t seem to have as much encoded knowledge about the native Mac development stack.

▲

Spivak an hour ago | parent [-]

This seems to be the inherent trade-off with smaller models. They can be just as "bright" as their larger contemporaries but they necessarily can't encode as much knowledge.

I think over time we'll realize this is the way forward, you want the smartest model with the least amount of embedded knowledge and you provide the knowledge externally or merge it into the weights for the domain you're interested in. Then you don't have to train a ginormous model every 6 months to pull in new information.

	▲	dcrazy 22 minutes ago \| parent [-]
		I think this is what the n-gram table in Qwen 4 (and 3.8-Flash-Next) is for. We’ll see if it comes down to the 27b variant. A RAG solution would make time to first token awful.