Codesota · Guides · Claude CodeFor readers who don't write codePublished December 2025
Guide · AI coding

Software, described in plain English.

Claude Code takes a description of what you want and produces the software that does it. No syntax, no frameworks, no command-line memory — the barrier shifts from can you code? to can you say what you want?

This guide is for the reader who has watched someone use Claude Code and wondered whether it is something they could do themselves. The short answer: yes.

§ 01 · Premise

What you are really doing.

The shape of the interaction, in one paragraph.

When you use Claude Code, you are describing a piece of software you want to exist — and something on the other end is reading your description, deciding what files to create, writing the code, running it, noticing when it does not work, and fixing it, until the thing you described actually exists. The novel part is not that a computer writes code. It is that the input is English rather than a programming language.

The practical consequence: the question of whether a piece of software should exist is no longer bundled with the question of whether you personally can build it. Those two questions have been inseparable for sixty years. They are separable now.

The rest of this page — the interactive explainer below — walks through the five things Claude Code does with your description, with small animations you can click through.

§ 02 · Walk-through

The five steps, one click at a time.

Understand · Plan · Build · Verify · Present. Each step has a short animation and a plain-English caption. Click through in order the first time.

Based on the idea by @seconds_0
Not affiliated with Anthropic. I just like their tool.

A Guide for the Non-Technical

Understanding Claude Code

Imagine you want to build a house. You know exactly what you want: three bedrooms, a big kitchen, lots of natural light. You can picture it perfectly.

But between your vision and that finished house stands an enormous wall: building codes, load-bearing calculations, electrical wiring, plumbing, permits.

Your Vision
THE WALL
Technical Knowledge
Reality

Claude Code removes that wall.

For software, you faced the same barrier. You needed to learn to code, or hire someone who could translate your vision into technical reality. Both paths have friction.

The Core Idea

Claude Code is like having a skilled contractor who lives inside your terminal and can read your mind.

You describe what you want in plain English, the same way you would describe it to a friend. Claude Code listens, asks clarifying questions when needed, and then actually builds the thing.

Months
Traditional development time
|
v
Minutes
With Claude Code
The barrier shifts from
"Can you code?"
to
"Can you describe what you want?"

How It Actually Works

Click each step to learn more

Click a step above to see how Claude Code works at each stage
The Magic of Iteration
If the result is not quite what you wanted, you simply say so. "Can you make the titles bigger?" or "I want to be able to rate each item." Claude adjusts, rebuilds, and presents again. You do not need to get your initial request perfect.

What You Can Actually Do With This

1

Automate tedious tasks

That spreadsheet you spend two hours updating every Monday? The files you manually rename? All of this can become a script that runs in seconds.

2

Build custom tools

Commercial software is designed for the average user. Claude Code can build software that fits you like a glove, because it only needs to fit you.

3

Transform your data

Have a folder of receipts to summarize? Customer feedback to categorize? Research papers to extract information from? Describe what you need.

4

Create websites and apps

Not just templates, but genuinely custom software. A portfolio site. A tool for your small business. An internal dashboard for your team.

5

Fix existing software

Something broken? Something almost-right that you wish worked differently? Claude can read existing code and modify it to match your needs.

The unifying theme:

Anything that could be done with software, you can now request in English. The remaining question is not "is it technically possible?" but "can you describe what you want clearly enough?"

A Concrete Example: Book Club Voting

Watch how a real conversation unfolds

You

I run a monthly book club and we vote on which book to read. I want a simple webpage where I can list the book options, members can vote, and I can see the results.

Getting Started: The Practical First Steps

1
Access
Get Claude Code from Anthropic's website and install it
2
Start simple
Open terminal, start with a trivial task to see the rhythm
3
Iterate freely
Your first description will be imprecise. That's fine.
4
Grow gradually
Start with small wins. Your intuition will grow with practice.
5
You are the expert
On what you want. Claude is the expert on how to build it.

Common Misconceptions

Click to reveal the reality

The deeper limitation to understand:

Claude Code is a tool that amplifies your ability to describe and iterate. The bottleneck shifts from "can I code?" to "can I clearly articulate what I want and provide useful feedback?" For most people, this is a dramatic improvement. But it does mean your success depends on your willingness to engage in the back-and-forth process of refinement.

The Bigger Picture

We are living through a genuine transition in how software gets made. For the first fifty years of computing, there was a priest class: the programmers who could speak the arcane language of machines. If you wanted software to do something new, you either became a priest or you paid one.

Claude Code represents something different. It is not about making programming easier. It is about making the need to program, for most purposes, optional.

This is not unlike what happened with writing. There was a time when literacy was rare and specialized. Scribes held power because they could read and write. Today, everyone writes, and the scarce resource is not the ability to form letters but the ability to form thoughts worth sharing.

Similarly, the scarce resource in the Claude Code era is not the ability to write code but the ability to imagine software worth building. Your ideas, your workflows, your specific needs become the raw material. Claude Code is the machine that transforms those raw materials into working reality.

You do not need to understand how it works any more than you need to understand how a car engine works to drive somewhere. What matters is that you know where you want to go and can describe the destination clearly enough for the journey to begin.

AK

A Programmer's Perspective

Andrej Karpathy on the current moment

"I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between."

"I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue."

The new landscape to master:
agentssubagentspromptscontextsmemorymodespermissionstoolspluginsskillshooksMCPLSPslash commandsworkflowsIDE integrations

"There's a need to build an all-encompassing mental model for strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering."

"Clearly some powerful alien tool was handed around except it comes with no manual and everyone has to figure out how to hold it and operate it, while the resulting magnitude 9 earthquake is rocking the profession."

"Roll up your sleeves to not fall behind."
- Andrej Karpathy, December 2025

Ready to Start? Use This Prompt

Copy this into Claude Code to begin with a guided interview

You are my dedicated software engineer. I am not technical, and that is perfectly fine. Your job is to handle all technical decisions so I can focus on what I want, not how it works.

Before we build anything, conduct a thorough interview to understand me and my project. This interview should feel like a friendly conversation, not a form. Ask one or two questions at a time.

About Me:
- Who am I? What do I do for work or life?
- What is my comfort level with technology in general?
- How do I prefer to receive updates?

About What I Want to Build:
- What problem am I trying to solve, in my own words?
- Who is this for?
- What does success look like?
- Are there any examples of things I have seen that feel similar?
- What absolutely must be included? What would be nice but not essential?

About Look and Feel:
- How should it feel to use?
- Are there colors, styles, or brands I want it to align with?

About How We Will Work Together:
- How do I want to give feedback?
- How often do I want to check in on progress?

Once you understand me, you have full authority over all technical decisions. Only bring decisions to me when they directly affect what I will see or experience.

Start the interview now. Be warm and conversational.
Try Claude Code

Available at claude.ai/code

§ 03 · Examples

What people actually build.

Five kinds of task that are a good starting shape for a first project.

Automate a tedious task
A script that reads a folder of PDFs, pulls out the invoice totals, and writes them to a spreadsheet. Thirty seconds to describe; thirty minutes of manual work saved every week.
Build a tool for yourself
A small app that tracks the books on your shelf, the meals you cook, the podcasts you rate — any record nobody else sells because the market is one person.
Transform or analyse data
Load a CSV, compute the thing you want, plot it, save the plot. The kind of task that used to require learning pandas and matplotlib before you saw any result.
Fix or modify existing software
Point Claude Code at a repository and describe the change. It reads the code, proposes an edit, applies it, and runs the tests.
Make a website
A landing page, a small site, a personal portfolio. HTML/CSS/JavaScript generated on request; no framework knowledge required.
§ 04 · Iteration

Your first try will be wrong. That is fine.

Claude Code is designed for conversation, not specification.

The mental model to avoid: “I have to describe the whole thing perfectly the first time or it will build the wrong thing.” That is not how this works.

The mental model to adopt: “I describe the thing I want, see what comes back, and say what to change.” The conversation is the tool. Your first description is a sketch; each reply is a revision.

The skill that matters is not writing long, precise specifications. It is noticing, in the result, the small way it differs from what you had in mind — and saying so.

Related · Further reading

Continue through the registry.