Claude on Time Friend

Audit Your Coding Habits with /insights

Mon, 27 Jul 2026 16:30:00 +0000

When you’re busy writing, you rarely stop to look at how you actually use your tools.

I’d been using Claude Code for a while, feeling pretty good about it. Then a friend said: “Try /insights.”

Start claude, hop into a session, and type:

/insights

Wait a few dozen seconds, and an HTML report pops up in your browser. It analyzes your last 30 days of Claude Code sessions and breaks them down: which projects you spent time on, which tools you used most, language distribution, and — the punchline — where your workflow is wasting tokens.

From Terminal to Team: When Agent Workflows Outgrow One Laptop

Sat, 18 Apr 2026 17:00:00 +0000

For the first few months, I used Claude Code alone in my terminal. Big productivity boost. But I hit a wall: when I closed my laptop, the agent stopped. Anything I needed had to happen while I was sitting in front of the keyboard.

If your usage is “only when I’m around”, Claude Code is plenty. But once you start thinking — can this code review run automatically? can this dependency update run every Monday? — you need it to work when you’re not there.

Reviewing Agent Code Is Different from Reviewing Human Code

Fri, 03 Apr 2026 13:25:00 +0000

Reviewing code written by a colleague is different from reviewing code written by an agent.

Work with someone long enough and you pick up their habits — one person loves reduce, another always misses edge cases. An agent has no habits. Every output depends on the session context.

Here are the checkpoints I’ve built for reviewing agent code.

First: did it touch things it shouldn’t have?

The agent’s biggest problem isn’t writing wrong code — it’s not controlling itself. It might fix one bug and casually modify a config file next to it, or rename a function that had nothing to do with the task.

Five Tasks You Shouldn't Give Your Agent

Sun, 22 Mar 2026 08:50:00 +0000

After a few months with agents, it’s easy to fall into the trap of throwing everything at it.

But some tasks really shouldn’t be delegated — not because the agent isn’t capable, but because the risk/reward ratio is wrong.

One: anything touching production data

Running SQL against a production database — even SELECT — I won’t trust an agent with. Claude won’t intentionally break things, but it might scan a full table because it misunderstood the query.

Agent and Assistant Are Not the Same Thing

Sat, 14 Mar 2026 15:40:00 +0000

When I first started using Claude Code, I spent a lot of time wondering: is this thing an agent or an assistant?

Most articles try to draw a clean line — assistant does one step at a time, agent pursues a goal autonomously. But after using it daily, the line is blurry. Most tools can switch between both modes.

The distinction that actually matters isn’t what you call it. It’s who initiates, who controls, and where it runs.

Claude Gets Dumber After 50 Rounds

Fri, 06 Mar 2026 11:10:00 +0000

After a few months with Claude Code, you’ll hit this: the same session, 50 rounds in, and Claude feels dumb.

It’s not your imagination, and it’s not the model. The context is blown.

How context explodes

Claude’s working memory is finite. Early in a session, it remembers the goal, the decisions made, and what’s left to do. By round 50, the context is packed with dead ends, discarded approaches, and arguments about implementation.

What I Put in My CLAUDE.md

Thu, 19 Feb 2026 16:20:00 +0000

The most ironic thing? Complaining “I have to re-explain the project to Claude every session” while your project root doesn’t have a CLAUDE.md.

Don’t laugh. I was in that exact spot.

Turns out there’s a shortcut — run /init. Claude analyzes your project structure, detects build tools and test frameworks, and generates a starting CLAUDE.md. If you already have one, /init suggests improvements instead of overwriting it.

What CLAUDE.md is for

Claude Code reads this file at startup and uses it as the starting point for understanding your project. How to run tests, how the directory is organized, what conventions to follow — put it there, and it just knows.

Would You Merge Code an Agent Wrote Alone

Thu, 05 Feb 2026 09:45:00 +0000

Claude finishes editing and says “Done.” You glance at it, looks fine, merge it. Then Monday comes and production is down.

Without a runnable check, the agent’s “done” and your “done” are two different things. The most expensive bugs aren’t crashes — they’re silent wrong answers.

The simplest check: one line in your prompt

Add this at the end of your prompt:

Run the tests after you finish. Keep fixing until they all pass.

Claude will run npm test on its own, check output, fix what’s broken, and rerun. No input needed from you.

Writing Prompts That Land on the First Try

Thu, 22 Jan 2026 14:15:00 +0000

After using Claude Code for a while, you’ll notice most failed sessions trace back to your prompt, not the model. Claude can infer intent, but you can’t expect it to read your mind.

Lock down the scope

“Optimize this code” — what comes out is a lottery. Optimize for what? Performance? Readability? Removing dead code?

A good prompt names the file, the scenario, and how to verify:

Write an edge-case test for logged-out users in src/auth.ts. No mocks.

The tighter the scope, the more predictable the output. Vague prompts only make sense when you actually want the agent’s opinion — “what would you improve in this file” is fine, but keep it scoped so it doesn’t wander into hundreds of files.

Keeping Your Agent on Track with Plan → Code

Thu, 08 Jan 2026 10:30:00 +0000

When I first started using Claude Code, I had a bad habit: open the terminal, type one sentence telling it what to change, watch it go, and realize later it went in the wrong direction.

Here’s what I learned — agentic coding is a different skill from writing code. When you write code yourself, your hands follow your brain. When you use an agent, your value shifts to defining the goal and reviewing the result. Not typing faster.