I think I can say with some confidence that Opus 5.5 has begun to reach a point in capability where it can solve most technical problems in a competent and acceptable manner. As a result, a vast majority of the decisions one needs to make when working with it have been boiled down to decisions of personal taste and opinion on design, rather than just focusing on what the most pragmatic solution is. Because matters of taste are far from objective, I think we’re going to begin to see more of a split in model offerings based on the kinds of taste each model has. If each model can do the work at an acceptable level from a purely utilitarian standpoint, then the only remaining decisions become how the model completes that work, and what sorts of decisions it makes with regards to styling, ui, ux, and so on. Many of these questions do not have definitive “correct” answers, and depend entirely on what appeals to the developer personally. Then, the model that becomes the most efficient to work with for you, is the one that shares your personal taste the most often, and has to be corrected the least amount during development. We’ve already begun to see this with Opus 5.5 as well, with people beginning to compliment not just its raw capability, but also its design sensibility and general taste with regards to ui and ux development. As models get smarter I think we’ll see a strata of models that have different “styles” emerge, to appeal to different types of individuals with different taste profiles. submitted by /u/DynaBeast
Originally posted by u/DynaBeast on r/ClaudeCode