I don't really think so. Maybe it's because the systems I build need to be reliable and understandable to humans, but I don't think Opus 4.6 is good enough to b

I don't really think so. Maybe it's because the systems I build need to be reliable and understandable to humans, but I don't think Opus 4.6 is good enough to be unsupervised. I've spent a lot of time using it and I have to tell it no semi frequently and rewrite by hand/iterate with the model frequently. It's saves me a lot of time when used this way, I think, but I still have to give it overall structure and keep it scoped to small changes to prevent it from going down wrong paths and generating tons of unnecessary code (which is how you end up with unmaintainable slop). Less code is pretty much always better and these models made it really easy to ignore that until it's too late. This is on a healthy mix of greenfield and brownfield projects. To that end, I've actually found Kimi K2.5 to be "good enough" for a lot of that, not quite as good at Opus 4.6, but good enough that it gets me like 80% of the value for a fraction of the cost and more speed.