Ok so after a break I dived in today with Opus 5.5. So far my experience has been: It takes instruction following to an extreme. You say one thing, and it lights some dynamite. My usual workflow is that the model can ‘get it’, but this is more like one thing moves it 5 steps forward and overshoots, then it overcorrects back, then I waste all this time on scoping that is normally much faster. The return to sane english is extremely welcome and overdue. It still says “carries” instead of “holds” for what a struct or object holds in terms of variables, so there is some obvious watermarking biases. It has made some surprisingly dumb decisions. E.g., what I assumed was obvious, and we agreed at a high-level provisionally, its interpretation of that was very wrong, and needed to be unwound. But this is in the same sense that I worked with say Fable or Opus 4.6 and it ‘worked’. The immediate sense is that obviously, I am yet to adapt to working effectively with the new model, and the usual trial and error to get a handle on this new motorbike needs some wearing in first. Hence, I thought I’d ask you that’s been in there for a few days - what’s working well for you with it ? What have you found is different to the previous models, and did you change anything in your workflow to get the best out of it ? Would love especially hear from people who are using it professionally at a senior engineering level not “I let it run and auto-accept its PR’s” given that it is clear (and kind of comforting) that it does still does still do slop and stupid decisions, namely for the fact that we still have a job for the time being. My typical workflow is have a ticket scoper, get that context locked in, parallelise ticket execution across sway sessions, monitor and follow up etc., if anyone is doing similar, otherwise welcome of course to all suggestions. Thanks submitted by /u/peterxsyd
Originally posted by u/peterxsyd on r/ClaudeCode
You must log in or # to comment.