Qwen3.6-35B-A3B solved coding problems Qwen3.5-27B couldn’t

· r/LocalLLaMA ·

Qwen3.6-35B-A3B demonstrates real-world coding capability gains over Qwen3.5-27B, solving architectural technical debt problems the prior model couldn't handle, suggesting notable improvement in the Qwen model family.

Categories: Model Releases

Excerpt

Yeah, another one of those new shiny model is better than previous SOTA, and I understand why you’d roll your eyes. I ignored Qwen3.6 for the first 24 hours thinking it’s overhyped like the last one, but eventually decided to put the doubts aside yesterday and set to try it Only against the issues Qwen3.5-27B simply couldn’t solve no matter how I tackled the issue. Qwen3.5-27B-Q4\_K\_M helped me build a customized budgeting app to replace a cloud-based one I used for almost a decade. It tracks expenses, income, builds dynamic budgets, imports/exports from bank accounts, built in charts, modern interface, and a bunch more little features. While it worked great, I just found that 27B was introducing technical debt as I kept on adding features. Once a week I’d do a few cleanups here and there, but at some point it hit a wall. I 100% thought it was Opencode limitation as 27B was eating up all the requirements that Qwen3-Next, Gemma4-31B and even Qwen3.5-122B couldn’t get. When Qwen3.6-35B-A3B dropped, I recalled my time testing the previous Qwen3.5-35B-A3B, and that was a giant waste of time at least for my project needs. Then yesterday, I broke after all the Positive posts in this sub and wanted to dive in again. The new 35B SLAPS! I pit it against all the failed implementations and bugs its 27B previous brother introduced, and it kept solving those either 1-shot or 2-shot at worst. Feeling motivated, I promoted it to review and tackle all code inefficiencies, and potent

Read at source: https://www.reddit.com/r/LocalLLaMA/comments/1soxyfi/qwen3635ba3b_solved_coding_problems_qwen3527b/

Discussions