The anxiety is real — and it’s everywhere

Open any Chinese developer community right now — Juejin, Major, or WeChat groups — and you’ll see the same posts dominating the timeline:

• “AI is already writing better code than I can. What’s the point of practicing anymore?”
• “I’ve lost all motivation to learn. AI knows everything I know, and more.”
• “Frontend development is a dead-end career. Start pivoting now.”

These posts routinely get hundreds of comments. The sentiment is unmistakable: a generation of developers who feel like they’re watching their own obsolescence in real time.

I know because I was one of them.

Three months ago, I was staring at a Cursor-generated component that was cleaner than anything I’d written all week. The sinking feeling hit hard — what am I even doing here?

But then something shifted. And it wasn’t because I ignored the AI wave. It was because I started using it.

The mental reframe: AI is not your replacement — it’s your force multiplier

Here’s the thing nobody tells you when you’re deep in the anxiety spiral: AI is the best thing that has ever happened to a curious developer.

Yes, it can solve the LeetCode problem you’re stuck on. Yes, it can generate a pixel-perfect landing page from a screenshot. But here’s what it can’t do:

• Understand your team’s business logic from a one-line Slack message
• Decide that the shiny new framework will actually be a maintenance nightmare six months in
• Push back on a bad product decision because you’ve seen this pattern fail before
• Build trust with stakeholders who need a human to say “I’ll own this”

Those things? That’s the actual job. The code was always the easiest part.

Once that clicked, my motivation didn’t die — it redirected. Instead of proving I could write every line myself, I started asking: what’s the highest-leverage thing I can do right now that AI can’t?

My actual daily workflow (tools and real scenarios)

I’m a frontend developer working on a side project — an English-language tech blog that covers Chinese developer tools and trends. Here’s how AI fits into my week.

UI prototyping: v0 / bolt.new

When I need to go from “rough idea” to “something I can click through,” I use v0 (Vercel’s AI UI generator). A typical session:

Prompt: "Create a blog post page with a dark mode toggle, reading progress bar,
and a sidebar with category tags. Use Tailwind CSS and a clean typography design."

15 seconds later, I have a responsive page. But here’s the key — I don’t copy-paste the whole thing. I cherry-pick the parts I like, refactor them into my existing component structure, and adjust the design tokens to match my system.

Time without AI: ~90 minutes of writing layouts, tweaking spacing, debugging responsive breakpoints.

Time with AI: ~20 minutes — and most of that is me thinking about what I actually want.

Code review and debugging: ChatGPT / Claude

I treat ChatGPT like a senior engineer who’s always available for a quick review:

• “Here’s my Astro component. The build passes but the dark mode flickers on first load. Spot the race condition.”
• “I’m using this Tailwind config. Is there a cleaner way to define these custom spacing tokens?”
• “Review this TypeScript type definition — am I over-engineering this?”

In every case, I’m not asking AI to do my job. I’m asking it to accelerate my learning. The output goes through my judgment, and I only apply what makes sense.

Code completion: Tongyi Lingma / Continue

For routine coding — wiring up APIs, writing boilerplate components, filling in TypeScript types — I use AI code completion as my auto-pilot. It handles the predictable 60% so I can focus on the tricky 40%.

The rule I follow: if the AI suggestion makes me think instead of just nodding, I type it myself. Because that’s where the learning happens.

Content creation: ChatGPT + DeepL

For my side blog (an English-language site covering Chinese developer tools), I use a translation-refinement pipeline:

1. Rough translation via DeepL from Chinese source material
2. ChatGPT rewrites for natural English technical writing
3. I do a final 10-15 minute review — fixing terminology, adding personal insight, and making sure the voice actually sounds like me

This pipeline turned a 4-hour-per-article process into 45 minutes. I’m not publishing AI-generated slop — I’m publishing my own analysis, just skipping the slowest part of the writing process.

The numbers: AI vs no-AI, same project

I tracked roughly how my side project changed before and after integrating AI into the workflow:

I’m shipping more, learning faster, and — critically — enjoying it more. Because I’m spending less time in CSS grid debugging hell and more time actually thinking about what I want to build.

The real threat isn’t AI — it’s refusing to adapt

Here’s my honest take, three months into this experiment:

AI won’t kill your motivation. It will kill the motivation of developers who measure their worth by how many lines of code they wrote today.

If your identity as a developer is “I can type React components faster than anyone,” then yes — AI is a threat to you. But that was never the valuable part of the job.

The valuable parts:

• Understanding the problem before writing a single line
• Knowing which tool or approach to use, and why
• Communicating trade-offs to non-technical stakeholders
• Building things people actually want to use

AI doesn’t touch any of that. It makes the easy parts faster so you can spend more time on the hard parts that actually matter.

So what now?

If you’re feeling the same anxiety I felt, here’s what worked for me:

1. Stop doom-scrolling AI replacement threads on Twitter/Reddit. They’re dopamine traps, not information sources.
2. Pick one AI tool and actually use it for a week. Not to replace yourself — to see what it can and can’t do. The gap is where you live.
3. Shift your metric of success. Stop counting lines of code. Start counting problems solved, decisions made, things shipped.
4. Invest in what AI can’t do: business understanding, system design judgment, communication, taste.

AI is a tool. A really, really good tool. And tools don’t replace craftsmen — they make them more dangerous.

I’m a frontend developer based in China, building Dual-Track Dev — a blog about Chinese developer tools and trends for a global audience. If you’re navigating the same AI anxiety, reach out or drop a comment. I’d love to hear how you’re handling it.