Are Engineers Banning Cursor? 

In a recent interview with Citadel Securities, Nvidia CEO Jensen Huang said that “100% of the company’s engineers now use the AI tool Cursor.” He described the adoption as part of a vision where “workforces in enterprise will be a combination of humans and digital humans,” crediting Cursor with delivering “productivity gains” and “better work.” Huang also listed Cursor among six AI startups he considers central to this new model, alongside OpenAI, Harvey, OpenEvidence, Replit, and Lovable.

While Huang’s remarks reflected strong endorsement from one of the world’s most valuable technology companies, the broader industry’s experience shows that adoption of tools like Cursor is far from frictionless. At San Francisco–based Mixus, resistance emerged almost immediately. Two software engineers declined to follow instructions to rely heavily on Cursor, convinced they could outperform the AI assistant.

Speaking to AIM Media House, co-founder Shai Magzimof was blunt. “Engineering teams should make Cursor (or an equivalent AI IDE) a daily, measurable standard: target 70–80% AI-assisted coding time per engineer, and track usage alongside outcomes (stories closed, PR cycle time, post-merge defects, coverage deltas). Treat these metrics as part of performance and team health reviews. ”

With just five employees, the standoff quickly became a major obstacle. Magzimof ultimately dismissed both engineers, one after only a week on the job. He attributed the pushback to ego. “If top-model access is constrained, prioritize budget toward enterprise Cursor credits and training so the team can consistently ship faster with higher quality backed by guardrails like human sign-off, secure-coding prompts, and audit logs of accepted vs. rejected AI suggestions. The goal isn’t to cut people—it’s to elevate people.” he said.