Claude vs ChatGPT vs Gemini for Real Work
I pay for more than one of these, which tells you the comparison is not as simple as picking a winner. Where each model is genuinely better, from daily use rather than benchmarks.
Benchmark tables are published constantly and they age in weeks. This is not one of those. It is what I notice when using all three inside real work: a QA job, WordPress builds, and design projects with actual clients waiting.
A caveat worth stating up front. These models update every few months, and a specific claim about which is better at task X has a short shelf life. What lasts longer is the shape of each one, which changes much more slowly than the scores.
Where Claude is the one I open
Long code, and anything where I need the model to hold a lot of context without drifting. Give it a full file and ask for a change and it tends to make that change rather than rewriting the surrounding code in its own preferred style. For work inside somebody else's codebase, which is most WordPress work, that restraint is the whole game.
It is also the one that most often says it is unsure. That reads as a weakness in a demo and as a strength at 6pm when you are deciding whether to trust an answer.
Where ChatGPT is the one I open
Breadth, and anything involving an ecosystem: a plugin I have not used, an API I do not know, a service whose docs are bad. Its coverage of the messy long tail of tools is noticeably wider.
It is also the better brainstorming partner. If I need fifteen angles on a problem rather than one good answer, it produces more variety.
Where Gemini is the one I open
Anything involving a large document or a lot of material at once, and anything inside Google's own ecosystem. If the input is a long specification or a set of reports rather than a question, it handles the volume well.
For a developer already working across Google's tooling, the integration is the argument more than the model is.
Things all three still get wrong
- Security defaults. None of them volunteer input sanitisation, nonces or capability checks unless you ask. All three add them correctly when you do.
- Version drift. All three will hand you a function deprecated years ago, because their training data spans the whole history of the platform.
- Confidence at the wrong moment. Ask any of them a question where the honest answer is "it depends on your setup" and you get a decisive answer instead.
- Your business rules. No model knows that your refunds close 24 hours before departure. That gap does not shrink with model quality.
So which one
If you are paying for exactly one and you write code for a living, I would take Claude. If you are paying for exactly one and your work is broader than code, ChatGPT. If your work already lives inside Google's tools, Gemini removes friction the other two cannot.
But the honest answer is that the difference between the three is now smaller than the difference between using one well and using one badly. A specific question with the relevant context attached beats a vague question to a better model, every time.
What I would check before subscribing
- Does it read your codebase, or only what you paste? This matters more than model quality.
- What happens to your code and your client's data? Check the retention policy before pasting anything under NDA.
- Can you switch models inside the tool? Being locked to one vendor in a field moving this fast is the real cost.
- Run your own three tasks through it before paying for a year. Benchmarks will not tell you how it handles your work.
Related
Task-by-task breakdown: which AI for which job. What breaks when you trust the output: vibe coding risks.
More posts
Every model is best at something and mediocre at something else. This is which one I open for which task, based on using all of them inside real client work rather than on benchmarks.
AI can write a WordPress plugin in a minute. Whether you should put that plugin on a live site is the part nobody covers. From someone who reviews this code for a living.
Most slow WordPress sites are slow for two or three specific reasons. Here is how to find which ones, in the order that gives you the biggest drop in load time for the least work.
AI can draft your test cases in seconds. Whether those cases find anything is a different question. What a year of using AI tools inside a real QA job actually changed.
AI writes the code in seconds. Someone still has to find out whether it works. A QA engineer’s view of what vibe coding actually costs, and how to use AI tools without shipping their mistakes.
Ten UX/UI trends worth knowing, sorted by whether they change what you actually build or just what design blogs look like this year.
A working checklist for hardening a WordPress site, logins, files, database, hosting and monitoring, written from what actually breaks on sites in production.
AI can lay out a screen, read behaviour data and run usability checks. It cannot decide what the product should be. A practical look at where the line sits.