Talking to Machines
EN
8

Chapter Eight

Speaking
the Language

The vocabulary of building —
not code, just the nouns and verbs.

You're about to sit down with a coding agent and build something. It's going to use words like "deploy," "endpoint," "component," and "schema." If those words are opaque, you'll feel lost — not because you can't build, but because you can't direct. This chapter gives you the decoder ring. Not how to code. How to speak the language of building.

Think of it like driving a car. You don't need to understand combustion engines, transmission ratios, or brake fluid pressure. You need to know: gas pedal, brake, steering wheel, mirrors. The vocabulary of direction, not implementation.

The Stack: A Decoder Ring

Every app — from Instagram to a simple to-do list — is built from four layers. Developers call this "the stack." Here's the whole thing, demystified:

Frontend

What people see and touch. Buttons, text, images, animations. The dining room of a restaurant.

Backend

The logic behind the scenes. Processes requests, checks passwords, sends emails. The kitchen.

Database

Where your app remembers things. User accounts, posts, settings. The pantry and recipe book.

Deployment

How it gets on the internet. Hosting, domains, going live. Opening the restaurant doors.

That's it. Every app you've ever used is some combination of those four layers. When your coding agent says "I'll set up the backend," it means "I'll write the behind-the-scenes logic." When it says "let's deploy," it means "let's put this on the internet." You don't need to know how any of these layers work. You need to know that they exist and what they're for.

The Agent as Tutor

Here's the part nobody tells you: the coding agent is also your teacher. Don't know what "npm" means? Ask. Confused by an error message? Paste it in and say "explain this like I'm not a developer." Want to know why the agent chose React over something else? Ask. It'll explain its reasoning in plain English, step by step, as many times as you need.

Your first five minutes

Open your coding tool. Describe your project in plain English: "I want to build a workout tracker where I log my exercises and see my progress over time." The agent will ask clarifying questions, suggest a stack, and start building. Your first job is to answer its questions and watch what it creates.

Explore the four layers of a web app. Click to learn the vocabulary — then test yourself.

The Stack Decoder

Click a layer to explore its vocabulary

The frontend is everything a user interacts with — buttons, text, images, forms, animations. It runs in the browser on the user's device.

Think of a restaurant. The frontend is the dining room — the menu, the tables, the decor. It's what customers experience.

Nouns (the things)
Component

A reusable piece of the interface, like a button or a card.

ReactVueSvelte
Page

A single screen or view in your app.

Home pageSettings pageProfile page
Style

How things look — colors, fonts, spacing, layout.

CSSTailwindSass
State

Data that can change — like whether a menu is open or a form field is filled.

Dark mode on/offItem count in cartCurrent tab
Verbs (the actions)
RenderDisplay something on screen. When a page renders, it becomes visible.
NavigateMove from one page to another.
Handle eventsReact to user actions like clicks, typing, or scrolling.

The backend is the server-side code that processes requests, applies business logic, and communicates with the database. Users never see it directly.

The backend is the kitchen. Orders come in, the kitchen prepares them, and sends out the finished dish. Customers don't see the kitchen, but nothing works without it.

Nouns (the things)
Server

A computer that listens for requests and sends back responses.

Node.jsPython/FlaskGo
API

A set of rules for how the frontend talks to the backend. Like a waiter taking orders.

REST APIGraphQLtRPC
Endpoint

A specific URL the frontend can call to get or send data.

/api/users/api/login/api/posts
Authentication

Verifying who a user is — login systems, passwords, sessions.

JWT tokensOAuthCookies
Verbs (the actions)
FetchRequest data from the backend. "The app fetches your profile from the server."
ProcessApply logic to data — calculate, validate, transform.
AuthorizeCheck if a user has permission to do something.

The database stores all the persistent data — user accounts, posts, settings, anything that needs to survive a page refresh or server restart.

The database is the pantry and the recipe book. It stores all the ingredients (data) and keeps them organized so the kitchen (backend) can find them fast.

Nouns (the things)
Table

A structured collection of data, like a spreadsheet. Each row is a record.

Users tablePosts tableOrders table
Schema

The blueprint for your data — what fields exist and what type of data each holds.

name: textage: numbercreated_at: date
Query

A request to find, add, update, or delete data in the database.

SELECT * FROM usersINSERT INTO postsDELETE FROM comments
Migration

A change to your database structure — like adding a new column to a table.

Add email fieldCreate orders tableRemove old column
Verbs (the actions)
StoreSave data so it persists. "Store the user's preferences in the database."
QueryAsk the database for specific data. "Query all users who signed up today."
MigrateUpdate the database structure without losing existing data.

Deployment is the process of taking your app from your computer and putting it on the internet where anyone can use it. It includes hosting, domains, and keeping things running.

Deployment is opening the restaurant. You've built the dining room, hired the kitchen staff, stocked the pantry — now you unlock the front door and put up a sign.

Nouns (the things)
Hosting

A service that runs your app on the internet 24/7.

VercelNetlifyRailwayFly.io
Domain

Your app's address on the internet — the URL people type to find you.

myapp.comcool-project.vercel.app
Environment Variables

Secret settings (like API keys) stored outside your code so they stay private.

API_KEY=abc123DATABASE_URL=...
Build

The process of converting your source code into optimized files ready to serve.

npm run buildProduction buildStatic export
Verbs (the actions)
DeployPush your app to the internet. "Deploy to Vercel" means put it live.
BuildPrepare your code for production — optimize, bundle, compress.
MonitorWatch your app for errors, slowdowns, or crashes after it's live.
Share this course
You don't need to know how the engine works. You need to know how to drive.

You know the words. You have the idea. Now it's time to sit down with your coding agent and actually build. Next: the art of the build loop — iteration, evaluation, and what to do when things break.

Complexity Score

New tool unlocked!