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?
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?
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.
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.
A RAG solution would make time to first token awful.
in your specific workflows, where specifically is the time to first token a dealbreaker? what's your typical target and what's a "no go"?
I don't think you meant to say this but it feels like you're saying "vibes".
It would be better to use a scoring framework like Harbor or similar?