And yes! I actually do this. I was barking up the wrong troubleshooting tree. That was… painful.

[6 hours later]

So funny story, it wasn’t useEffect 🫣

Reminds me of the interesting fact that we put the man on the moon (1969) before we put wheels on luggage (1970).

Also: ensure there’s some guiding lights in said document. Like “no file greater than 800 lines of code, keep it modular with long term maintainability in mind”

And I know at least one business owner who confessed even if tariffs go away, prices will stay the same given people are willing to pay for it. I suspect it will be like gas prices. Quick to go up, slooooow to go down.

I realized I could take it a step further. Told it to write a design guide based on this much better view. Wrote it all up in markdown for me, app wide style guide. I just now include it in every context prompt and… yeah. Insane.

To be fair, the latest version of Cursor has gotten a LOT better due to it seeing linter errors and iterating on that (even raising the white flag recently for me saying I should check docs—less hallucinating). But times (sliver rarer now)when you chase the tail. I give it 2 lives now. Then Google.

Right now having some success using it as an interface against some internal APIs (discord bot). Finding myself using it more than Postman interface.

Cursor for the vibing. Expo for local iOS emulator dev (hot reload is pretty nice). Although haven’t been using expo for the iPhone standalone build (got a simple script for that + Xcode). Been focused on iOS first since I’ve got that, but plans to be cross platform.

NGL, this is bookmarked for me.

ohshitgit.com