Some collected words about Cursor
Since March, I have used Cursor on and off for plenty of tasks. For example, I did a complete Redux to Redux-Toolkit migration for one project, in which I learned a lot. Mostly, for which tasks I should use Cursor and which not. If you start with Cursor, you should use it to implement a bigger feature, to learn all the quirks. It will take time, and I value the time using it for the Redux→RTK migration. And now, I typically use Cursor for smaller tasks. Or just break down the bigger ones and enhance them so they are suited for Cursor.
For a while, I struggled with the right model. The auto mode worked in some way, but I was not perfect. So I tried to explore the models directly and wanted to learn, which I can use for which task. But since Claude released Sonnet 4, I exclusively use this model for everything. It is astonishing how well Sonnet 4 works.
Recently, I have found a good workflow. I collect some Tasks and execute them one by one. And while Cursor/Sonnet 4 is thinking and working, I do some chores in the House. Which is a Win-win for all of us here. 😅
I trust Sonnet 4 so much, that I'm thinking of trying out Claude Code. Which, in theory, fits better into my terminal workflow. Cursor is a fork of VSCode which is too much UI distraction for me. But I appreciate the diff tool, which works good for me. And I never found a good one for the terminal.
21 of #100DaysToOffload
#log #dev #cursor
Thoughts? Discuss...