Coding help and Claude Code, for non-engineers and builders

0:00 Claude and code

You do not need to be a developer to get real value from Claude's coding skills, and if you are a developer, Claude Code changes how you work. In this lecture, non engineers will learn a safe pattern for formulas and small scripts, and builders will see how Claude Code works inside a real codebase, plus the governance questions every team should ask first.

0:28 Why this matters for everyone

Why should non engineers care about code? Because a surprising amount of office work is small, repetitive processing. Renaming files, cleaning a spreadsheet, moving rows between sheets. A ten line script can remove hours of that every month. But code also acts on real data, and a mistake can overwrite something important. Think of it like a power tool. Enormously useful, and you still wear safety glasses. The safe habits in this lecture let you get the benefit without the damage.

1:03 Two modes

There are two modes. Coding help in chat means asking for a formula, a script or an explanation of an error, and Claude can even run code in a sandbox to test it. Claude Code is different. It is Anthropic's agentic coding tool. It works directly in your codebase, reading files, planning changes, editing across many files, running commands and tests and using git, asking permission according to the mode you choose. It runs in the terminal, in VS Code and JetBrains, in the desktop app, on the web, and in Slack.

1:43 The safe snippet pattern

For non engineers, use the safe snippet pattern. Say you are not a developer and name the tool, for example Google Sheets. Describe the goal in plain English. Then ask for three things, the formula or script, a plain English explanation of each part, and three test rows including an edge case. If a script changes files or data, always test on a copy of a small sample first, and keep backups. And never paste passwords or API keys into prompts or scripts.

2:19 Claude Code: first moves

For builders, install Claude Code from Anthropic's official documentation, open your project folder, and type claude. Run the init command to generate a CLAUDE dot M D file, which holds project guidance Claude reads at the start of every session, such as build commands, conventions and what not to touch. Then ask for a plan first. Read the codebase and propose a plan to add a size guide to product pages, do not edit yet. Approve the plan, then work in small, testable steps.

2:56 A good CLAUDE.md

A good CLAUDE dot M D is short and specific. The stack. The commands to run lint and tests before saying a task is done. Folders it must never edit, like production config. Local requirements, for example that Arabic right to left and English layouts must both be checked. And a rule to keep changes minimal and explain any new dependency. Keep it current, because a stale guidance file quietly produces stale behaviour.

3:28 Extending Claude Code

You can extend Claude Code. MCP servers connect it to tools like issue trackers, databases and design files. Skills package procedures that load only when relevant. Subagents handle focused sub tasks with their own context, such as writing tests. Hooks run your own scripts at set moments, like formatting code after every edit. And plugins bundle all of these for sharing across a team. If you are building your own agents, the Claude Agent SDK packages the same harness as a library for your own infrastructure.

4:05 Simple example

A simple example. In Google Sheets, you want column D to say overdue when the date in column C is before today and the status in column E is not paid. Ask Claude for the formula, a plain English explanation of each part, and three test rows including an edge case. You get the formula, an explanation you can actually follow, and test rows, one overdue, one paid, one due tomorrow. Paste them in, confirm the results, then apply the formula to your real sheet. That is the safe snippet pattern in action.

4:45 Worked example: a three-day job in one

A two developer agency in Dubai needed an internal tool that turns a campaign CSV export into a weekly PDF summary. The lead developer wrote a CLAUDE dot M D, asked for a plan, approved it, and let Claude Code build the script in small steps with tests. She reviewed every diff, added a hook that runs the linter automatically, and kept the API key in an environment variable. A three day job took one, and the code went through exactly the same review as human written code.

5:23 Governance first

Before adopting agentic coding across a team, answer five questions. What can it access, repositories, production systems, secrets? Which permission mode will you use and who approves risky actions? How are AI written changes reviewed, tested and attributed? Where do secrets live, and the answer must never be in prompts or committed files. And on business plans, which admin controls and usage analytics will you switch on?

5:52 Try this now

Try this now, and choose your lane. If you are not a developer, pick one spreadsheet or file problem that annoys you every week. Use the safe snippet pattern, ask for the formula or script, a plain English explanation and test rows, and try it on a copy of a small sample first. If you are a builder, open Claude Code in a non critical repository, run init, edit the generated CLAUDE dot M D so it contains your real commands and rules, and complete one small task plan first, reviewing the diff before accepting. Either way, write down one thing you checked before trusting the result.

6:39 Watch me do it, part 1

Let me show both lanes. First, the non engineer lane. I paste the safe snippet prompt. I am not a developer, I use Google Sheets, show overdue in column D when the date in column C is before today and column E is not paid. Give me the formula, a plain English explanation, and three test rows. Claude returns an IF formula with AND and TODAY, and explains each part. I open a copy of the sheet, type the three test rows, one overdue, one paid, one due tomorrow, and the results are exactly right. Only then do I fill the formula down the real column.

7:25 Watch me do it, part 2

Now the builder lane. In a small repository for a weekly PDF report tool, I type claude, then run init. It generates a CLAUDE dot M D, and I edit it to list the real commands, npm test and npm run lint, plus rules, never commit secrets and keep changes minimal. Then I ask for a plan first. Read the code and propose how to add a currency column to the PDF, do not edit yet. The plan has four steps, and I approve it. Claude makes the change and runs the tests. In the diff I notice it added a formatting library, so I ask it to use the existing helper instead. Tests pass, and I commit.

8:16 Recap and next step

Recap. Everyone can use the safe snippet pattern, ask for explanations and test rows, and always test on copies. Builders get the most from Claude Code with a clear CLAUDE dot M D, plan first, small testable tasks and reviewed diffs. And every team should answer the governance questions before scaling. Your next step: non engineers, solve one spreadsheet problem this week. Builders, run init on a non critical repo and ship one small task plan first.