I'm Not a Dev But I Use Qwen 3.6 35b to Code

Posted by thejacer@reddit | LocalLLaMA | View on Reddit | 73 comments

Full disclosure: I used to program a bit, but I was garbage at it so I found a new career. This was eons ago so I'm not a dev, obviously.

There's been a few posts the last couple of days highlighting struggles with these small models and coding so I wanted to just share what worked for me, and this isn't a "use this harness" or "this agent did the thing" kind of post. Keep in mind, I'm not a dev, I never even learned modern development strategies or anything like that so if this is obvious to some of you actual programmers just forgive me and move on, if it sounds stupid...well it works, so...

The thing that changed vibe-coding for me was having the LLM write and run very thorough tests. I don't know if I was doing something wrong before but the LLM didn't recommend this (GLM 5, Kimi K2.5, Gemini 3.0 Pro, Claude Sonnet...) but more and more I noticed people mentioning tests and iterative development that I just couldn't get my system to do...turns out after I prompted the LLM to write tests it would and then it runs these tests after every change and makes corrections. With this I've managed to get substantially better work done with Qwen 3.6 35b than even Kimi K2.5 (prior to tests obv...).

Previously I would ask the LLM to add a feature or fix something and something else would end up broken or modified in some sort of way. This held true for Claude Sonnet 4.5 and Kimi K2.5, while Qwen3.5 122b, 27b and 35b were absolutely useless. Since incorporating these tests I've got working features that Kimi K2.5 (via Moonshot API) kept getting half assed, and its been done with Qwen 3.6 35b.