Everyone is t/s maxing.. 3.8.. but after a week of using it for work I'm tempted to switch back to 3.6
Heat trend
Collecting trend data
The percentage is based on available heat signal, not comment count or independent people.
A developer is considering switching back to Qwen 3.6 from 3.8, despite 3.8's advanced coding capabilities. While Qwen 3.8 is praised as a "damn good coder," it is criticized for being a "terrible collaborator." The user notes that 3.8 struggles to maintain a consistent code style and often introduces overly complex solutions, such as strict type checks, for simple internal methods, unlike 3.6 which seamlessly integrates small changes.
> "Qwen 3.8 is a damn good coder, but a terrible collaborator"
It modifies SO many things in my scripts for what should be a 2 line PR, I get a 100 line linter style mess that looks like a high school freshmen got his hands on vs code and pushed code in.
It can't maintain a common style, if I give it a script with a certain naming and layout, 3.6 one shots small changes that fit into my structure. 3.8 will add code that looks much more advanced, handling, strict type checks. But if it's just my internal method that gets called in exactly one place, it is way overkill code
3.8 produces DAMN GOOD code, but will get stubborn on wanting it's own parameters and return types. A simple return False works for my particular use case, but here goes Qwen formatting me the perfect return dict full of useful metadata
Am I crazy?