Discussion about this post

User's avatar
Yorwba's avatar

I'd like to add that removing Claude Code from employee computers doesn't mean they completely stopped using it. About a year ago, Alibaba employees told me they'd been given access to Claude via an internal platform where they could define tasks and have them run in a cloud workspace, without ever touching their computer. Clearly, somebody had thought ahead to limit the risk of leaking sensitive company data and code.

When this news broke, I asked them what happened to running Claude in the cloud, and they told me that using Claude Code on their own (well, the company's) computer is just much more convenient and the model is better than what they get in Qoder.

It's a bit like a chemistry lab installing a glove box with a fume hood to handle dangerous materials, later getting a complaint about samples contaminated with coffee, and it turns out everyone is just mixing stuff in the lab kitchen because the gloves are too annoying.

China Product Signals's avatar

Your caveat about IDC capturing on-paper adoption rather than actual usage feels like the key product question. A useful comparison would score the same coding task on four dimensions: accepted PR, human review time, policy-compliant access, and data-boundary violations. That could explain why a domestically procured tool wins the market-share survey while developers still route around it. It also turns “decoupling” from a binary claim into an observable workflow change.

3 more comments...

No posts

Ready for more?