Not worth $40/month

Discussion
1

Here is my experience… create a great app…works perfectly… ask to make small change in the CSS… app breaks forever. Tell me this hasn’t happened to any of you. My God… it’s how this application works…lol… I don’t know… I think using Claude is just more efficient.

2

As every instrument, you need to know how to use it. happends every time with newbies, you need to know how to give correct instructions, to give context and to review the code that the llm is changing for furter adjustments

2 Likes
3

please, please, please, learn how to use git

6 Likes
4

In general, the quality of the output is going to directly relate to the quality of the input. So if you’re finding that your requests are not giving you the results you want, you should rethink how you’re instructing the model.

A couple good practices to protect you against the scenario you described:

  • when Cursor merges its code change into your codebase, scan the file to check if Cursor is wiping out code it shouldn’t before you accept the changes. I’ve found a buggy merge is the number one way Cursor can seriously break you codebase. When this happens, you’ll typically see a HUGE red block where Cursor is incorrectly wiping out code. Cursor’s merge logic has come a long way in the last couple months and I find this is far less of an issue than it used to be, but this is a good practice. If you find this keeps happening, consider breaking your file into smaller files or adding tags that help Cursor better delineate the subsections of the code.

  • use git and use git often. VS Code allows you to commit to git with just a couple clicks and this is a great way to back up your code so you can always rollback if things go sideways. Every time you get to a stable point, commit. Cursor also has Checkpoint links in the Composer window. You can use these links to rollback changes Cursor has applied

Hope this helps! I encourage you to stick with Cursor and try implementing practices to mitigate these kinds of issues. Once I started using these strategies, I was able to avoid any major problems from a bad merge.

1 Like
5

Claude is already used under the hood. Sounds like you aren’t double checking changes Cursor is making. That and/or bad prompting + giving wrong context.

6

Honest everyone_question: Directions to perfect GIT use?

I gh CLI the F out of my bots and they still ■■■■ bits…

===

May you plz share expertise?

7

Yo I noticed you dont like AI in your AI so I took AI out of AI ing you r AI into your experience into AI so I give you BASIC goto 10