Why Programmers Are Addicted to Claude After a Month of Use

After a month of using Claude, the author shares insights on its advantages over ChatGPT, particularly in coding and text analysis.

Why Programmers Are Addicted to Claude After a Month of Use

I was a heavy user of ChatGPT for nearly two years. Last month, a developer friend insisted I try Claude, and eventually, I registered out of annoyance.

A month later, I canceled my ChatGPT subscription.

This isn’t because ChatGPT is bad; rather, Claude is indeed superior in certain aspects. Today, I will share my genuine experiences without exaggeration.

Image 3

The First Difference: Code Review

Although I’m not a professional programmer, I often write Python scripts for data processing and occasionally review others’ code.

In ChatGPT, I typically paste a piece of code and ask, “Are there any issues with this code?” It can identify some obvious bugs, but usually stops there.

The first time I used Claude for the same task, I pasted a Python script of about 200 lines. It not only found bugs but also pointed out:

  • The code crashes when handling null values.
  • The third-party API call lacks timeout handling.
  • A variable name is misleading.
  • It suggested restructuring the overall code into three independent functions.

Then it provided a refactored version, explaining each modification.

Honestly, at that moment, it felt like switching from an “AI that can chat” to “a colleague who truly understands code.”

Artifacts Feature: An Underrated Killer Feature

Claude has a feature called Artifacts, which means when you ask it to generate code, web pages, or charts, it doesn’t just paste the code in the chat window for you to copy. Instead, it opens a sidebar to directly show the running effect.

For example, when I asked it to “generate a web page for data analysis dashboard,” it rendered an interactive web page in the sidebar, where the charts could be clicked, zoomed, and filtered. If I was unhappy with the effect, I could simply say, “Change that bar chart to a line chart,” and it would modify it on the spot.

This experience is completely different from ChatGPT. In ChatGPT, you have to copy the code to your local environment to see the effect, and if you want to make changes, you have to copy it again.

My practical use case: When creating data reports, I first use Claude’s Artifacts to quickly produce a visual prototype, confirm that the layout and colors are satisfactory, and then use other tools to create the final version.

Long Text Processing: What 1000K Context Means

Claude 4 supports a context window of 1000K. What does this mean? It’s roughly equivalent to 750,000 words.

In simple terms, you can throw an entire book, a whole project codebase, or dozens of documents at it and let it perform cross-analysis between these contents.

I attempted an extreme test—feeding it the entire codebase of an open-source project (about 200 files) and asking, “What is the core architecture of this project? If I want to add a payment module, which files should I modify?”

It not only accurately described the project architecture but also listed six specific files that needed modification, explaining what changes were required in each file and even suggesting the order of modifications.

This level of understanding is something I haven’t experienced with other AI tools.

Writing Quality: Indeed a Step Above ChatGPT

This may vary from person to person, but at least for me, this is the case.

When I had both models write the same content—like a product introduction copy—ChatGPT produced a coherent and well-structured text, but it had a somewhat “AI flavor” to it. Claude’s writing felt more natural, with phrasing and sentence construction resembling human writing.

Another noticeable difference: Claude is more willing to express uncertainty. For instance, if I asked it a question it wasn’t sure about, it would directly say, “I’m not very sure, but based on what I know…” ChatGPT tends to provide an answer that appears confident, even when it might not be.

I personally prefer Claude’s style—honestly telling you it is uncertain is much better than confidently giving you a possibly incorrect answer.

However, Claude Also Has Its Frustrations

1. Access Issues in China

This is the biggest pain point. Claude cannot be accessed directly in China and requires a VPN. Moreover, its API and web version have high stability requirements for proxies, leading to occasional connection failures.

Sometimes at home, it suddenly disconnects while I’m using it, forcing me to switch nodes and reconnect, which can take several minutes. This experience is genuinely frustrating during high-intensity daily use.

2. The Free Version is Too Limited

After registering, the free version allows about 50 messages per month. Sounds like a lot? It runs out quickly with just two messages a day. For someone like me who needs 20-30 rounds of dialogue daily, the free version is simply insufficient.

The Pro version costs $20 per month (about 145 RMB), which isn’t outrageous, but it’s pricier than DeepSeek’s free version and Kimi’s 199 RMB—especially considering it lacks localized Chinese support.

3. Poor Image Generation

This is not a big deal for me since I don’t use it for drawing. However, if you need an all-in-one AI tool, Claude does have shortcomings in image generation.

4. Ecosystem and Plugins are Inferior to ChatGPT

ChatGPT has a GPTs store, a plugin ecosystem, and extensive third-party integrations. Claude is still quite closed in this regard, primarily offering a web interface and API without much expansion.

My Current Usage Pattern

After a month of use, my AI tool combination has become:

  • Code writing, code review, data analysis → Claude (its capabilities are indeed strong)
  • Reading long documents, conducting industry research → Claude (the 1000K context advantage is too significant)
  • Creative writing, brainstorming → ChatGPT (its creative abilities are still stronger)
  • Daily simple Q&A and Chinese content → Kimi or DeepSeek (free, good in Chinese, convenient)

Claude isn’t perfect, but in its strong areas—coding, long texts, and in-depth analysis—it is currently the best.

Image 4

A Few Words for Those Considering Trying It

  1. Try the free version first. Although 50 messages aren’t many, it’s enough for you to determine if it meets your needs.
  2. If you are a programmer or need to handle large amounts of text, Claude is worth paying for. $20 a month offers good value for professional users.
  3. If you only use it casually, DeepSeek and Kimi’s free versions might suit you better. There’s no need to use a VPN just for occasional use.
  4. Definitely try the Artifacts feature. Whether you write code or not, this feature will allow you to intuitively feel the difference between Claude and other AIs.

After using Claude, my biggest takeaway is that AI can be more than just a “chatting tool”; it can be a true partner that helps you get work done. Although access issues in China are troublesome, if you’re willing to put in some effort, it’s worth it.

Was this helpful?

Likes and saves are stored in your browser on this device only (local storage) and are not uploaded to our servers.

Comments

Discussion is powered by Giscus (GitHub Discussions). Add repo, repoID, category, and categoryID under [params.comments.giscus] in hugo.toml using the values from the Giscus setup tool.