[curiouser3]

Cursor has been a really interesting journey for me. I've built an entire Elixir/Phoenix browser MMO, but I have almost no confidence that I've done things idiomatically. Adding rules to urge the agent to be more "idiomatic" doesn't provide confidence.

Additionally, Elixir does not really lend itself to automated coding since the message/event based flows don't make dependencies obvious, and typing is soft and not-enforced statically. Adding rules like "always call mix xref callers <module_name>" or "run compile command" after each change has been helpful, but I still end up with bugs where changes in one part of the app cause runtime errors that are not only tricky to diagnose, but require multiple iterations of logging and manual debugging - which becomes costly when each Cursor agent costs me 4 cents. Perhaps this is standard for Elixir, or maybe I need to be architecting my code patterns in a smarter way.

The most frustrating part is how much of a yes-man the agent is, it would be really nice to be able to have the agent steer me away from decisions where the code is being written against best practices. I agree with the author's sentiment - The "learning moments" I run into seem to be whenever Cursor screws something up and I have to investigate myself, rather than a sort of learning-with-guidance while doing it right.