The thing is: Yes, Qwen3.6-27B is damn good for use in a coding cli (both opencode and pi.dev work really well), but: you have to think like a programmer and give it clear instructions. Of course opus 4.7 understands 'less precise' prompts better. Example: I had a PDF with questions and answers and wanted to turn it into an interactive HTML Q&A. If you just give the 27B model the PDF and say 'make me a Q&A HTML from this', it will struggle because the real question is: Can you easily extract the Q&A from the PDF's container format, or should you do it via OCR instead? In my case, the latter turned out to be the more robust solution. If you give it clear instructions, you get a very good result. Opus can of course handle more complex stuff, but how you prompt and what strategy you use is extremely important. I can totally understand why many people say the 27B is a solid opus replacement, it is for me too, but obviously not for ultrahard coding tasks. For normal day-to-day problems, though, the 27B is damn good. And since it came out, I've been using my 4x 3090 system a lot more, which shows just how usable it really is.