Model review in coding sessions

#7
by Throghar - opened

I must say model is fast, it handles tool calls very well, but its weak in coding and it just picks wrong solutions to simple problems, overengineering etc.

@Throghar Thanks for the candid feedback. Could you share one simple task where it chose the wrong approach, along with its response and what you expected instead? A redacted example is fine. Which quantization, runtime/agent and sampling settings were you using? We'd like to reproduce the failure rather than explain it away with benchmark scores.

well it was used to fix .net maui blazor hybrid app and i wanted it to fix a bug in mediaelement "player" and it started speculating and overengineering thread safety measures while the approach didnt need it because it was natively thread safe. Also same thing with trying to overengineer bug in search method in razor.cs page with debounce implementation it started to rewrite whole debounce mechanics adding interlock etc...

Another example: trying to solve problem with js and more complex approach instead of searching docs with mcp for native framework approach.

All of those were decisions that i had to stop the model in its work and explicitly tell it to do something else.

I cant share the app code though, so at least i hope this will be helpfull.

Quant from bartowski Q5_K_L
runtime: Ante terminal

@Throghar Thanks for the concrete examples — they're helpful even without the app code. We'll look into the unnecessary rewrites and framework choices and try to improve this in the next version.

Sign up or log in to comment