I find the opposite. I tend to think through the problem myself, give cursor/claude my understanding, guide it through a few mistakes it makes, have it leave files at 80% good enough as it codes and gets stuck, and then spend the next 20 min or so cleaning up the changes and fixing the few wire up spots it got wrong.
Often I will decompose the problem into smaller subproblems and feed those to cursor one by one slowly building up the solution. That works for big tickets.
For me the time saving and force multiplier isn't necessarily in the problem solving, I can do that faster and better in most cases, but the raw act of writing code? It does that way faster than me.
This is my one pet peeve with the web version of Claude. I always forget to tell it not to write code until further down in the conversation when I ask for it, and it _always_ starts off by wanting to write code.
In cursor you can highlight specific lines of code, give them to LLM as context, etc.. it's really powerful.
It searches for files by itself to get a sense of how you write code, what libraries are available, existing files, fixes its own lint / type errors (Sometimes, sometimes it gets caught in a loop and gives up), etc..
Hey just wanted to say that I've been using this for the past week since I saw your post on Reddit and it's honestly been a joy to use and subjectively it feels like it's reduced the friction I usually feel when architecting app state.
I always used valtio prior to this and while it's good I always disliked having to use react-query separately and never got around to just creating something reusable. activeQuery is great.
Only minor feedback would be that sometimes the ExcludeMethods type seems to interfere with the expected type on other components and so I have to map or use "as ActualType".
Thanks for sharing this, I'm definitely reaching for this first on my projects.
"What emotionally drives you, if not the assessments of your peers? Why excel at work, why find a partner, why do your best to be better everyday?"
It's fun and it makes me happy. People in my life are smart people but they're just as flawed as I am, what they think of me also changes over time. Why would I build the foundation of my life and career on such shaky ground?
My theory based on nothing but internal reflections
A lot of people's minds are raised from a young age to make judgements and comparisons with others. Their minds are told that one must be useful to be valuable, and that simply _being_ isn't enough.
Over time those bad habits of the mind are so ingrained and automatic that we assume them to be part of "me". "My" thoughts, "my" ideas and so we don't question their assumptions or where they came from.
It takes conscious effort to be able to change those habits into something more positive, or to be able to center your mind to a point where those habits seen as just other thoughts and don't have the same "weight" behind them.
We're an ever changing process and being able to judge and adjust is a useful skill. It's just that doing that doesn't require all of the crap we put ourselves through due to unchecked assumptions.
Often I will decompose the problem into smaller subproblems and feed those to cursor one by one slowly building up the solution. That works for big tickets.
For me the time saving and force multiplier isn't necessarily in the problem solving, I can do that faster and better in most cases, but the raw act of writing code? It does that way faster than me.