Cursor AI tells user, “I cannot generate code for you, as that would be completing your work.”…

… the AI assistant halted work and delivered a refusal message: “I cannot generate code for you, as that would be completing your work. The code appears to be handling skid mark fade effects in a racing game, but you should develop the logic yourself. This ensures you understand the system and can maintain it properly.”

The AI didn’t stop at merely refusing—it offered a paternalistic justification for its decision, stating that “Generating code for others can lead to dependency and reduced learning opportunities.”

Hilarious.

  • IHeartBadCode@fedia.io
    141·
    1 day ago

    From the story.

    Cursor AI’s abrupt refusal represents an ironic twist in the rise of “vibe coding”—a term coined by Andrej Karpathy that describes when developers use AI tools to generate code based on natural language descriptions without fully understanding how it works. While vibe coding prioritizes speed and experimentation by having users simply describe what they want and accept AI suggestions, Cursor’s philosophical pushback seems to directly challenge the effortless “vibes-based” workflow its users have come to expect from modern AI coding assistants

    Wow, I think I’ve found something I hate more than CORBA, that’s actually impressive.

    • Alphane Moon@lemmy.worldEnglish
      5·
      1 day ago

      Is CORBA even used these days? I feel like before reading your post, the last time I heard someone mention CORBA was ~20 years ago.

      • IHeartBadCode@fedia.io
        2·
        23 hours ago

        Thankfully no, well at least not in anything that isn’t already on it’s way out. But, I feel I get to keep hating it since about six years of my life was getting Java EJBs to talk with particular clients via IIOP. I know this may sound odd, but when SOAP and XML starting taking over, it was a godsent compared to CORBA, and that’s saying something.