Skip to content
build-3000
fundamentals

What Is Software?

Programs, files and running code - the words behind the magic.

Objective

Explain what a program is, where software lives on your machine, and use the words file, folder, app and source code correctly when talking to your AI agent.

Vocabulary

The words to use when directing your agent.

program
A list of instructions a computer follows in order.
source code
The text version of a program that humans read and edit.
file
A named container for data on your computer - code, text, images are all files.
folder
A container that groups related files together.
application
A program made for people to use - a notes app, a game, a website.

Understand it

Instructions, not intelligence

A program does exactly what its instructions say - nothing more. This is also true of your AI agent's output: it writes instructions for computers. Reading those instructions (the code) is how you stay the director.

Where software lives

Every app starts as a project folder somewhere on your disk. The folder holds the code files, settings files and assets. Knowing 'it is all just a folder' removes most of the fear.

Core concepts

Code is text, software is action

Source code is plain text until something runs it. Your AI agent edits text files; the computer turns them into behavior. When people say 'run the app', they mean 'execute these instructions'.

Everything is a file

Your app's code, its settings, its images and even the record of what your agent did - all files in folders. If you can organize files, you can organize software.

Examples

A calculator button

When you tap '=' in a calculator app, a few lines of code take the numbers on screen, add them, and put the result back. That whole feature can be under ten lines of text.

This curriculum site

The page you are reading is files: layout files, style files and data files. A build step turned them into the site. Nothing more mysterious than that.

Common mistakes

Common mistake

Assuming the AI agent 'understands' your goal the way a person would.

Fix

State the goal, the inputs and what 'done' looks like. The agent fills gaps by guessing - guesses you have to review.

Common mistake

Never looking at the files the agent creates.

Fix

Open each new file once and ask the agent for a one-line summary. You are not learning to write code yet - you are learning to recognize it.

Working with your AI agent

When your agent scaffolds anything, follow up with: 'List every file you created and describe each in one sentence.' Make this a reflex from day one.

Build it

The module’s real project. Your agent builds; you direct and inspect.

Project: Vocabulary Notebook

Have your agent build a single-page notebook that lists every term you learn in this curriculum - term on the left, meaning on the right. You will extend it as you learn.

Requirements

  • One HTML file that opens directly in a browser by double-clicking it
  • Shows at least five terms with their meanings in a readable list or table
  • You can add a new term by asking the agent (and later, by copying the pattern yourself)

Context for your agent

Build a single self-contained HTML file called notebook.html with inline CSS. It must render a titled list of term-meaning pairs stored in one obvious place in the file so a beginner can find and copy the pattern. No JavaScript frameworks, no build step, no external dependencies.

Verify it - twice

Check every item yourself first. Then hand your agent the prompt and compare verdicts.

Self-verified0/6
Functional
Architecture
Testing

Verification prompt - paste into your AI agent

Review my Vocabulary Notebook project. I asked my coding agent to build a single self-contained HTML file listing at least five term-meaning pairs. Check my actual file against this checklist and answer PASS or FAIL for each item with one line of evidence from the file itself: (1) opens standalone with no server or dependencies, (2) five or more term-meaning pairs present, (3) terms defined in one clearly marked place, (4) no external libraries or network requests. Then tell me: which assumption in my instructions most likely caused any FAIL, and the smallest fix.

Run this against “What Is Software?” after your own checklist pass. Where the agent and you disagree, investigate before moving on.

Review questions

Answer out loud. If you cannot, revisit before moving on.

  1. In your own words: what is the difference between source code and a running program?

  2. Your agent created four files. What question do you ask before trusting any of them?

  3. Why is 'it is all just files in a folder' a useful thing to know?

You can now

  • Use the words program, source code, file, folder and application accurately
  • Ask an agent to explain every file it creates
  • Open and inspect an HTML file without fear

Up next

Terminal Basics