Earlier quoted context omitted.
Did anyone say that? They are an issue everywhere, including for code. But with code at least I can have tooling to automatically check and feed back that it hallucinated libraries, functions etc, but with just normal research / problems there is no such thing and you will spend a lot of time verifying everything.
You get some superficial checking by the compiler and test cases, but hallucinations that pass both are still an issue.
Cursor IDE support hallucinates lockout policy, causes user cancellations
321–330 of 635 posts
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#322Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#323Earlier quoted context omitted.
You're giving the game away when you talk about the joy LLMs are robbing from you. I think we all intuit why people don't like the idea of big parts of their jobs being automated away! But that's not an argument on the merits. Our entire field is premised on automating people's jobs away, so it's always a little rich to hear programmers kvetching about it being done to them.
I naively bought into the idea of a future where the computers do the stuff we’re bad at and we get to focus on the cool human stuff we enjoy. If these LLMs were truly incredible at doing my job I’d pack it up and find something else to do, but for now I’m wholly unimpressed, despite what management seems to see in it.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#324Earlier quoted context omitted.
You’ve promised a ton of people refunds that never got them. Others in this thread, and myself included Edit: he did refund 22 mins after seeing this
you didn't get a refund because the promise of refund was also hallucinated.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#325Earlier quoted context omitted.
I use it all the time, and it has accelerated my output massively. Now, I don't trust the output - I review everything, and it often goes wrong. You have to know how to use it. But I would never go back. Often it comes up with more elegant solutions than I would have. And when you're working with a new platform, or some unfamiliar library that it already knows, it's an absolute godsend. I'm also damn proud of my own…
> "and it has accelerated my output massively." The folly of single ended metrics. > but to avoid LLMs out of principal? That's just luddite. Do you double check that the LLM hasn't magically recreated someone else's copyrighted code? That's just irresponsible in certain contexts. > in case you feel it relevant. Of course it's relevant. If a 19 year old with 1 year of driving experience tries to sell me a car using t…
I frankly do not care, and I expect LLMs to become such ubiquitous table-stakes that I don't think anyone will really care in the long run.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#326surely it wouldn't backfire, right???
ok aside from the joke from this case alone, I think we can all agree that AI not replacing human soon
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#327Earlier quoted context omitted.
Clearer would have been: "AI controlled support assistant of Cursor".
True. And maybe they added that to the signature later anyway. But OP in the reddit thread did seem aware it was an AI agent.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#328Earlier quoted context omitted.
I use it all the time, and it has accelerated my output massively. Now, I don't trust the output - I review everything, and it often goes wrong. You have to know how to use it. But I would never go back. Often it comes up with more elegant solutions than I would have. And when you're working with a new platform, or some unfamiliar library that it already knows, it's an absolute godsend. I'm also damn proud of my own…
I have a hard time being sold on “yea it’s wrong a lot, also you have to spend more time than you already do on code review.” Getting to sit down and write the code is the most enjoyable part of the job, why would I deprive myself of that? By the time the problem has been defined well enough to explain it to an LLM sitting down and writing the code is typically very simple.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#329Earlier quoted context omitted.
They already rolled out an "AI" product. Got humiliated pretty bad, and rolled it back. [0] [0] https://www.bbc.com/news/articles/cq5ggew08eyo
They had an opportunity to actually adapt, to embrace getting rapid feedback/iterating: But they are not equipped for it culturally. Major lost opportunity as it could have been a driver of internal change. I'm certain they'll get it right soon enough though. People were writing off Google in terms of AI until this year.. and oh how attitudes have changed.
that's the problem noo?? big company is sucks at that, you cant do that in certain company because sometimes its just not possible
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#330Cursor sucks. Not as a product. As a team. Their customer support is terrible. I was offered in writing a refund by the team who cold reached out to me to ask me why I cancelled my sub one week after start. Then they ignored my 3+ emails in response asking them to refund, and other means of trying to communicate with them. Offering me a refund as a bait to gain me back, then when I accept it they ghost me. Wow. Very…
I had the same exact experience - after disappointment (couldn't use like 2/3 of my premium credits because every second request failed after they upgraded to 0.46) unsubscribed. They offered refund in email. I replied I wanted refund but no reply