Frustrated software developer believed AI-generated message came from human support rep.
See full article...
See full article...
LinkedIn is flooded with terrible takes about how we like, won't need version control anymore, mannnn, like GitHub you know? Because our code will just like be the prompts, and the prompts are your code, mannn.Vibe coders using an LLM driven workflow given wrong information by an LLM chatbot that they didn't error-check.
Completely on-brand for vibe coders. (Full disclosure I use Github Copilot for low-stakes refactors, line autocompletes, and trivial API lookups. But I error check statically damnit.)
Narrator: Though the reason for the cancellations had changed, the cancellations continued because coders want humans to help them deal with issues caused by AI-generated vibe coding subs."Hey! We have no such policy," wrote a Cursor representative in a Reddit reply three hours later. "You're of course free to use Cursor on multiple machines. Unfortunately, this is an incorrect response from a front-line AI support bot."
Narrator: Though the reason for the cancellations had changed, the cancellations continued because coders want humans to help them deal with issues caused by AI-generated vibe coding subs.
So, question: If you can continue to use Cursor on multiple machines, why didn't that particular coder experience the continuity of doing that across multiple machines?
Sounds like they still have a problem, and no current fix for it.
And what do you think the model you're vibe coding with is trained on…?I never was much of a coder, but I've been vibe coding like crazy. It produces insanity a lot, but if you're careful and focused you can get some real gold out of it. It helps that most people are pretty fucking stupid to begin with and most things out there are complete trash, so the bar is low.
So question on that. How would they of checked that the support email response was valid and from a person?Vibe coders using an LLM driven workflow given wrong information by an LLM chatbot that they didn't error-check.
Completely on-brand for vibe coders. (Full disclosure I use Github Copilot for low-stakes refactors, line autocompletes, and trivial API lookups. But I error check statically damnit.)
Does he have an MBA?My engineering director at work recently asked me how I can use AI to help me speed up my development, like using it to do cross-platform development between android and iOS and web, without knowing the other platforms or languages. We already don't have any QA team, and now they're prodding more and more vibe coding. I didn't think much of him before this meeting (too much hearing himself talk, fatuous questions), but now any respect I had is gone.
I haven't checked, but my guess is yes. He seems to get by on schmoozing and has the same offputting aura that I get from MBAsDoes he have an MBA?
…should not of….
Hey, I just wanted to let you know that it’s “should have” and “would have.” The increasingly common error “should of” stems from the spoken version of the contraction, “should’ve”, “could’ve”, “would’ve.”How would they of…
Then you're still not much of a coder.I never was much of a coder, but I've been vibe coding like crazy. It produces insanity a lot, but if you're careful and focused you can get some real gold out of it. It helps that most people are pretty fucking stupid to begin with and most things out there are complete trash, so the bar is low.
Didn't these things already cause several deaths from suicide and such?It's only a matter of time before one of these dumb things gets somebody killed.
"made the policy up" "invented"While I appreciate Benj's diligent work on the AI beat, I remain disappointed at the uncritical acceptance and parroting of the anthropomorphizing language the industry uses to build its hype train, i.e. "confabulation", "hallucination" etc. Why not "error", "random output", "bad data", or if we want to be technical, "bullshit"?
How do we know that was the chatbot? Maybe the email was from a person, and the later post "correcting" the email was the actual chatbot?I love the response from the chatbot. “We limit a given session to a single device as a core security principle. Anyway, you can pay more for the functionality”
Unfortunately, this doesn't seem to be the most important criteria for management in too many instances.No doubt this would absolutely be frustrating, but as someone working in a Support capacity I have to admit it's a little validating to know that A.I. still can't do my job.
Don't worry. In an attempt to solve the problem, they'll spend greater and greater sums of money, which is similar to your idea.If a human tech support made up a fake policy, lying to the customer and embarrassing the company, he would be fired.
Good bot.Hey, I just wanted to let you know that it’s “should have” and “would have.” The increasingly common error “should of” stems from the spoken version of the contraction, “should’ve”, “could’ve”, “would’ve.”
Cheers!![]()
If a human tech support made up a fake policy, lying to the customer and embarrassing the company, he would be fired.