Cursor in agent mode + Sonnet 3.7 love nothing better than rewriting half your codebase to fix one small bug in a component.
I've stopped using agent unless its for a POC where I just want to test an assumption. Applying each step takes a bit more time but means less rogue behaviour and better long term results IME.
Reminds me of my old co-worker who rewrote our code to be 10x faster but 100x more unreadable. AI agent code is often the worst of both of those worlds. I'm going to give [0] this guy's strategy a shot.
If you stopped using agent mode, why use Cursor at all and not a simple plugin for VSCode? Or is there something else that Cursor can do, but a VSCode plugin can't?
Building a RN app without any features (authentication, notifications) is easy - but adding those features and then navigating the outside-app ecosystem isn’t. It’s definitely not like the web.
Strange that LlamaParse is mentioned in the pricing table but not the results. We’ve used them to process a lot of pages and it’s been excellent each time.
> The core issue, however, is the inability to participate in the actual craft. Design decisions are buried in React components with cryptic expressions like flex items-center shadow-lg p-6 hover:bg-gray-50 dark:bg-gray-800 py-[calc(theme(spacing[2.5])-1px)]
Give me Tailwind standardised utility classes over having to search through the codebase to find what a dev 6 years ago called a CSS class.
I'm a Python fan condescending on PHP, but doesnt the world still depend on deploying instantly via FTP and cheap hosts enjoying the low overhead of a 100000 sites on a server? On the other hand, cheapest Namecheap and Digitalocean plans are neck to neck on first glance.
I've stopped using agent unless its for a POC where I just want to test an assumption. Applying each step takes a bit more time but means less rogue behaviour and better long term results IME.
reply