← Back
SL
Siddharth Lamba
·May 2026·7 min read

I Gave an AI My Terminal. Here's What Happened.

A developer's honest first look at Claude Code — the tool that made me feel like I was pair programming with someone who actually knew what they were doing.


AI ToolsDeveloper ExperienceClaude Code
~ claude
✓ Claude Code initialized. How can I help?
> refactor my auth module and add tests
Reading project... analyzing 14 files...
Writing auth.service.ts

Let me set the scene. It's 11pm. I've been staring at the same authentication bug for two hours. My stack trace is useless. My coffee is cold. And then a coworker drops a link in Slack: "Have you tried Claude Code yet?"

I hadn't. I'd used ChatGPT for code snippets before — copy, paste, tweak, repeat. The usual dance. But Claude Code promised something different: a tool that actually lives in your terminal and works with your codebase. Not a glorified autocomplete. A collaborator.

Skeptical but desperate, I typed npm install -g @anthropic-ai/claude-code and hit enter. What followed was one of the more surprising evenings I've had as a developer.

I asked it to explain a 200-line function I barely understood myself. It came back with a diagram in my terminal. An actual diagram.

The first five minutes

Setup was embarrassingly easy. After installing the package globally, you just navigate to your project and type claude. No config files, no API key hunting, no documentation walls.

The first thing I did was describe the bug in plain English — "my JWT refresh token fails silently after a certain timeout, only in production" — and it asked to see the relevant files. Not a copy-paste prompt. It reached into my filesystem, read the code, and reasoned through it out loud.

# My first real Claude Code session
> can you look at src/auth/token.service.ts and tell me why refresh might fail silently

Reading token.service.ts... (247 lines)

Found a likely issue: Line 89 — the catch block swallows the error
and returns null instead of rethrowing. In production, the expired
token check on line 103 then receives null and treats it as "no token"
rather than "invalid token", silently redirecting to login.

Fix: throw the error from the catch block, or return a typed
error object. Want me to make that change?

It found the bug. In under a minute. The bug I had been staring at for two hours.

What actually makes it different

Here's the thing about most AI coding tools: they're context-blind. You paste in a snippet, they respond to that snippet. Claude Code removes that translation layer — it reads your files, navigates your project structure, and matches your existing patterns.

Pro tip I learned the hard way: Be specific about what you want it to not touch. Say "refactor the token validation logic in token.service.ts, leave everything else untouched."

The honest verdict

I've been using Claude Code weekly for two months now. The file wrangling, test scaffolding, and "I know what I want but don't want to type it all out" tasks all go to Claude now.

The bar isn't 'can it write all my code.' It's 'does it make me faster and less frustrated.' The answer is yes.

That 11pm auth bug? Fixed in four minutes. The cold coffee was still worth finishing.

312 claps
SL

Siddharth Lamba

Developer writing about tools, workflows, and the occasional 11pm debugging session. Building things on the internet.