mplorentz on Nostr: Cursor's Composer 2 model is performing much worse for me than Composer 1 :( I feel ...
Cursor's Composer 2 model is performing much worse for me than Composer 1 :( I feel like Composer 1 really hit a sweet spot for me between speed and quality.
For me the bottlenecks for coding with AI are:
- understanding all the code that the model wrote
- testing changes
Composer 1 really helped with the first because it could blast out small amounts of code that I could quickly review without my brain getting bored and context switching to something else. I feel like I'm an outlier in that I'm trying to stay heavily involved in the dev flow rather than having a multiple agents work on long tasks and then coming back in cold to review their work. Is anyone else using smaller quicker models in this way?
Published at
2026-04-15 16:33:58 UTCEvent JSON
{
"id": "afef7bd629a1bc078a085d55613ffab72b910862e442fc0a8238e3535480bfd6",
"pubkey": "d0a1ffb8761b974cec4a3be8cbcb2e96a7090dcf465ffeac839aa4ca20c9a59e",
"created_at": 1776270838,
"kind": 1,
"tags": [],
"content": "Cursor's Composer 2 model is performing much worse for me than Composer 1 :( I feel like Composer 1 really hit a sweet spot for me between speed and quality. \n\nFor me the bottlenecks for coding with AI are:\n- understanding all the code that the model wrote \n- testing changes\n\nComposer 1 really helped with the first because it could blast out small amounts of code that I could quickly review without my brain getting bored and context switching to something else. I feel like I'm an outlier in that I'm trying to stay heavily involved in the dev flow rather than having a multiple agents work on long tasks and then coming back in cold to review their work. Is anyone else using smaller quicker models in this way?",
"sig": "11b79c5a767923de884207c225def4ff055e11162fda65a1d265182dd1b59eb68419950525ecc2714b8988565427c2479f826df3eed47a83d08d780696775088"
}