Claude, the AI assistant built by Anthropic, has quietly become the tool I open more often than my browser’s search bar. But watching friends try it for the first time, I notice the same pattern: they type one vague sentence, get a mediocre answer, and conclude “AI is overrated.” The gap between that experience and what Claude can actually do is mostly technique. Here is what I would tell someone starting today.
Where to use it
There are three main doors into Claude, and picking the right one matters:
- claude.ai — the web app, plus mobile and desktop apps. This is the general-purpose door: writing, analysis, translation, summarising documents, thinking through decisions. You can upload files (PDFs, spreadsheets, images), and paid plans add Projects — persistent workspaces where you store context once (your style guide, your codebase docs, your standard templates) instead of re-explaining it every conversation.
- Claude Code — a terminal-based agent for developers. Instead of pasting code snippets back and forth, Claude works directly in your repository: it reads files, runs tests, fixes bugs, and opens pull requests. If you write software, this is the single biggest upgrade — the difference between a consultant you describe your codebase to and a colleague who has actually cloned it. (This very blog was scaffolded, styled, and deployed by Claude Code.)
- The API — for building Claude into your own products and automations.
The five habits that change everything
1. Give context before the question. Claude cannot see your screen, your job, or your last email. Compare “write an announcement” with “write a 100-word announcement for our internal Slack, friendly tone, telling a 20-person engineering team that deploys are frozen this Friday for database maintenance.” The second prompt costs you fifteen seconds and saves three rounds of revision.
2. Show, don’t describe. If you want a particular style, paste an example of it. If you’re asking about an error, paste the whole error message — not your summary of it. If you want a document reviewed, upload the document. Claude is dramatically better at pattern-matching from real material than at guessing from adjectives.
3. Iterate instead of restarting. The first answer is a draft, not a verdict. “Shorter.” “More formal.” “Keep paragraph two, rewrite the rest.” “Now the counter-argument.” Each follow-up compounds, because Claude remembers the whole conversation.
4. Make it think before it answers. For anything with reasoning involved — a legal question, an architecture decision, a tricky bug — ask Claude to lay out its reasoning, list its assumptions, or argue both sides before concluding. You will catch mistakes in its reasoning that you would never catch in a confident final answer.
5. Ask it to critique, not just create. Some of Claude’s best work is adversarial: “find the weaknesses in this contract clause,” “review this code for edge cases,” “what questions will the auditor ask about this report?” Turning it into a red team is often more valuable than turning it into a ghostwriter.
What to watch out for
Claude is a reasoning engine, not a database. For anything factual and consequential — laws, prices, medical claims, citations — treat its answer as a well-informed first draft and verify the source (or let it use web search, then check the links). Never paste real secrets: API keys, customer data, anything covered by an NDA. And know when to stop delegating: Claude drafts, you decide. The signature at the bottom of the document is still yours.
A note for Vietnamese readers
Claude handles tiếng Việt well — translation in both directions, drafting emails, even explaining legal and administrative documents. My favourite trick for language learning: paste a paragraph you have written in English or Vietnamese and ask “correct this, then explain each correction as if I’m an intermediate learner.” It is a patient tutor with unlimited office hours.
Start small: pick one recurring task this week — the weekly report, the code review, the email you always postpone — and hand Claude the first draft of it. Technique grows from there.