# What AI Anxiety Sounds Like in Chinese Developer Communities > Source: > Published: 2026-08-10 08:00:10+00:00 My last post — the one about AI not killing my motivation — did something I didn't expect. A few hundred people read it in a week. A handful of people commented. A lot of you followed. I was genuinely surprised. Reading through the responses, I noticed something I had not expected: **the fear sounds different here from the English-language developer discussions I read every day.** In many English-language discussions, AI anxiety is framed as an existential question: In the Chinese communities I read and take part in — Juejin comments, V2EX threads, and WeChat developer groups — the emphasis is often somewhere else: The difference is not absolute, but it is noticeable. One conversation often asks: **"Will AI replace me?"** The other often asks: **"Will AI help someone else replace me?"** Those questions overlap, but they lead to different practical concerns. China's developer market was intensely competitive long before AI arrived. Terms such as "996" — 9 AM to 9 PM, six days a week — are part of the career conversation, whether people are describing job postings, past experience, or the pressure they expect from the market. In that environment, the question is often less *"will a tool replace me?"* than *"who becomes more competitive once this tool is widely available?"* AI changes what a team can expect from each person. That does not mean a junior suddenly becomes a senior. Context, review judgment, and ownership still matter. But AI can shorten the distance between an idea and a plausible implementation, so the baseline for routine work can move faster than people expect. That is why, in the communities I follow, AI anxiety often appears as tool FOMO rather than a debate about craft: *"Which model are you using?" "Have you tried Tongyi Lingma?" "Is Cursor worth paying for?"* The conversation is usually tactical. In a competitive market, refusing to try a useful tool can feel less like a principle and more like a risk. The recurring tension is simple: someone may want to keep their skills sharp, while also worrying that a team already using AI will move faster. That is the part of AI anxiety I hear most often here. A few weeks back, I saw a thread where a developer asked: *"My whole team started using AI tools. I refused — I wanted to keep my skills sharp. Now I'm the slowest one. Am I wrong?"* The top reply: *"You're not wrong. You're just going to be unemployed and right."* That, in one sentence, is the Chinese developer AI anxiety in a nutshell. If you're a Chinese developer over 30, you already know this term: **the 35-year-old cliff (35岁危机)**. It refers to a widely discussed concern that age can narrow opportunities in parts of the technology job market. The reality varies by company, role, city, and individual situation, but the concern is familiar enough that it shapes career decisions well before someone reaches 35. AI did not create this fear. I heard versions of it from more experienced developers when I was a junior, and it still comes up whenever people talk about layoffs, career changes, or whether to keep specializing. What AI changes is the feeling of how quickly the market can move. If AI helps a less experienced developer complete more routine work, it can make the usual questions about experience, cost, and speed feel more immediate. That does not prove that AI creates an age cliff, but it can make an existing anxiety sharper. That is why I see people say versions of: *"I'm more worried about turning 33 than about GPT-5."* They are not necessarily dismissing AI. They are ranking it alongside the pressures that already affect their jobs. In conversations I have had, layoffs are usually discussed in terms of budgets, business changes, and cost. AI becomes part of that discussion because it may change what a smaller or cheaper team can deliver. Here's a question you see constantly in English-language AI discourse: *"If AI writes my code, am I still a real developer?"* I have read this framing many times. I see it much less often in the Chinese communities I follow. Why? I think it comes down to how developer identity gets built in each context. In some English-language open source and indie-hacking circles, the craft of writing code is closely tied to developer identity: typing the solution, understanding every line, and being able to recreate the stack from scratch. AI can feel disruptive because it puts a layer between the developer and the code. In the Chinese teams and communities I know, the balance often tilts more toward outcomes: shipping the product, meeting the deadline, and getting through the release. If a tool helps a team move faster, people are usually willing to try it. That does not make the code less important; it changes what gets emphasized in day-to-day work. Neither orientation is better. They simply put the pressure in different places. The equivalent concern I hear more often is: *"If AI removes my speed advantage, what is my edge now?"* One assumption that does not travel well is that GitHub Copilot is the default tool for every Chinese developer. In the communities I know, it is not. Network access and payment can add friction to some international tools. Developers I know use domestic alternatives — **Tongyi Lingma** (Alibaba's AI coding assistant), **CodeGeeX** (from Zhipu AI), or chat interfaces such as DeepSeek, Qwen, and GLM — alongside international tools. The stack often looks different from the "Cursor + Copilot + Claude" setup treated as a default in some English-language discussions. This matters because the day-to-day AI experience can be less integrated than some product demos suggest. A multi-tool workflow — code completion in one place, chat-based debugging in another, then copying a revised function back into the codebase — has different costs and risks from an AI-native IDE workflow. The gap between what a model can do in a demo and what it can do reliably in a real workflow still matters. That gap shapes both productivity and anxiety. Many developer jobs sit outside big tech: small and medium companies, outsourcing teams, and traditional industries going through digital transformation. In China, this is often discussed as part of the **sinking market (下沉市场)**. These jobs often look nothing like the clean "AI is replacing us" narrative. The codebase may be old, requirements may change in conversation, and important business rules may exist only in the head of the one senior dev who's been there since 2015 and never documented anything. The system can be several applications connected by manual work and a shared spreadsheet. Current AI tools do not remove the work of sitting in meetings, clarifying what a client means, and turning incomplete business context into a workable specification. That work is not only about writing code. It is about translating a moving, sometimes contradictory business situation into decisions a team can implement. That complexity can limit what automation changes in the short term. It does not make those jobs safe, and it does not make the work less skilled. It means AI adoption looks different when the bottleneck is unclear ownership, incomplete requirements, or business context rather than typing speed. In other words: the automation can't even figure out what the job is. That's a different kind of moat. Not AI alone, and not always in the "will a model replace me" framing common in some English-language discussions. The concerns I hear most often are **speed** — how quickly AI can narrow an existing advantage — **age**, and **refusing to adapt**. In a competitive market, standing still rarely feels neutral. If you're a developer reading this from outside China and feeling the same existential dread about AI, here's what I'd offer from inside the Chinese dev bubble: The Chinese developer communities I know are not less concerned about AI. The concern is often shaped by a different labor market, different tools, and different day-to-day constraints. And the monster we're actually afraid of? It's usually the one that shows up. *I'm a frontend developer based in China, writing Dual-Track Dev — a blog about Chinese developer tools and trends for a global audience. If you're navigating the same AI anxiety from wherever you are, drop a comment. I read every one.*