Set up your own benchmark test. Run several models through meaningful workflows. I run local models every day and the harness is key for squeezing performance out of smaller models. I'd estimate that, depending on the work you're doing of course, you could get Qwen3.5:27B to within 80% code quality if you spent some some time fine tuning your harness specifically to that model and your workflow. It would be a lot of trial and error testing, and I've done a ton of it, but the results are pretty nice. I use mostly Qwen3.5:122b-a10b but its the same family and the harness I've developed for it has made a huge difference as it has evolved over time.
Set up your own benchmark test. Run several models through meaningful workflows. I run local models every day and the harness is key for squeezing performance out of smaller models. I'd estimate that, depending on the work you're doing of course, you could get Qwen3.5:27B to within 80% code quality if you spent some some time fine tuning your harness specifically to that model and your workflow. It would be a lot of trial and error testing, and I've done a ton of it, but the results are pretty nice. I use mostly Qwen3.5:122b-a10b but its the same family and the harness I've developed for it has made a huge difference as it has evolved over time.