If you’ve spent any time recently in founder conversations, developer Slack groups, or investor WhatsApp chats, one pattern keeps coming up:

“Have you tried Claude Code yet?”

What’s interesting is not just that people are talking about it but who. This isn’t limited to hardcore engineers. Increasingly, it’s investors, operators, and “non-technical” power users who are making Claude Code part of their daily workflow.

Claude Code isn’t just another AI coding tool. It represents a deeper shift in how people interact with LLMs for work.

To find out what all the hype is about, and what it means for investors, I spent the xmas break to nerd out, get deep into the Claude Code rabbit hole, and launched this free Slack “Automation Experiment” group (glad to see 350+ of you already in there, sharing your workflows & ideas) so we can learn from each other.

In today’s episode, I’ll share:

This episode is your single source of truth to understand why you should start using Claude Code as a non-technical person and how to set it up so you can start automating your work.

Now.

Most AI tools still live in the browser.

You ask a question, you get an answer, you copy-paste, and context is lost almost immediately.

Claude Code breaks that pattern.

The core reason for the hype is simple: Claude is exceptionally good at reasoning over real codebases and projects, not just isolated snippets.

It can read large files without falling apart, understand how different parts of a project connect, and follow multi-step instructions without drifting off into hallucinations.

Just as importantly, Claude Code lives inside the workflow. It sees your actual files, your folder structure, and your previous changes. You don’t have to re-explain context or paste half a repo into a chat window. Claude becomes persistent.

And maybe the most underrated feature: it’s boring in the best possible way.

Claude Code doesn’t try to be overly agentic. It doesn’t randomly rewrite half your project or deploy things you didn’t ask for. It does exactly what you tell it to do and shows you what changed.

That predictability is why serious users trust it.

But to be clear: Claude Code isn’t the only option. If anything, the opposite is true: We’re spoiled for choice.

There are endless comparison tables listing features, benchmarks, and pros and cons. But in practice, most of those miss the point.

What really differentiates these tools is not raw intelligence or speed. It’s how they behave once a project starts to evolve.

A useful way to think about this is gravity.

Gravity, in this context, means: How strongly the work wants to stay in one place as it changes over time.

Take the current generation of vibecoding tools. They all promise fast progress but they create very different kinds of projects.