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

Reddit r/LocalLLaMA / 4/18/2026

💬 OpinionSignals & Early TrendsTools & Practical UsageModels & Research

Key Points

  • A user reports that Qwen3.6-35B-A3B can solve coding problems that Qwen3.5-27B could not, improving performance for their specific development tasks.
  • They used Qwen3.5-27B-Q4_K_M to build a customized budgeting app (expense/income tracking, dynamic budgets, bank import/export, charts, and UI features), but it accumulated technical debt as features grew.
  • After hitting a wall they suspected model/context/feature limits, they tried Qwen3.6-35B-A3B and found it fixed earlier bugs and inefficiencies with minimal extra passes (often 1-shot or 2-shot).
  • In an agent workflow with constraints (e.g., splitting work into subagents and staying within a 128k context window), the model produced a clean report in ~20 minutes and then completed implementation work in ~30 more minutes.
  • On an RTX 5070 Ti 16GB, the Q5_K_XL variant performed around ~320 tokens/s for processing and ~50 tokens/s for generation, with minor issues such as not fully respecting “Plan mode” and needing oversight to avoid unwanted file writes.

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 potential security risks. Asked it to use subagents to split the work and never go above the 128k context window. About 20 mins later it produced a pristine report of what to do, then flipping the agent to Build mode took it another 30 mins to address everything.

On my 5070 Ti 16GB, the Q5_K_XL is pretty good. ~320t/s processing, and 50t/s for generation it thinks too much but rarely goes into any loops. It has some wrinkled areas still like it doesn’t respect the Plan mode in Opencode and ends up writing files, but I promoted around it to avoid that for now. If you had doubts or thought this ain’t for me, just give it a shot. It won‘t be a waste of time at the least.

If the new Qwen team can improve so much upon the last 35B, how would the new 27B do?!

submitted by /u/simracerman
[link] [comments]