Start here
New to building software with AI?
This page teaches the words and the shape of the work — no product pitch, no jargon left unexplained. Ten minutes here makes everything else on this site, and most of what your AI says, make sense.
What building an app actually involves
Whatever you're building, the work follows the same loop. AI speeds up every step — it doesn't remove any of them.
- 1
Decide what you're building
One sentence: who is it for and what can they do with it? Everything else flows from this.
- 2
Describe it to your AI
In plain words, one piece at a time. Small, specific asks get much better results than 'build my whole app'.
- 3
The AI writes code — you read the result
You don't need to understand every line. You do need to check it does what you asked, and ask the AI to explain anything surprising.
- 4
Test it
Click through it like a stranger would. Better: have tests — small programs that check your app automatically, every time it changes.
- 5
Ship it
Putting your app on the internet where real people can use it. This is called deploying, and it's a repeatable step, not a one-time event.
- 6
Improve it — forever
Real apps are never finished. You'll fix, add, and reshape continuously; the loop above just keeps turning.
The words you'll meet, in plain English
Twenty terms cover most of what you'll hear in your first weeks. None of them is complicated — they just usually go unexplained.
The building blocks
- Frontend
- The part of your app people see and click — the pages, buttons, and forms in the browser.
- Backend
- The part that runs behind the scenes on a server — checking logins, saving data, doing the real work.
- API
- How two pieces of software talk to each other. Your frontend asks the backend for data through an API; your app can use other companies' APIs too (like Stripe for payments).
- Database
- Where your app's information lives permanently — users, orders, messages. If it must survive a restart, it belongs in the database.
- Framework
- A pre-built foundation you build your app on top of, so you don't start from zero. Next.js and Rails are frameworks.
- Dependency
- Someone else's code your app uses instead of writing it yourself. Apps typically have hundreds; keeping them updated matters because their bugs become your bugs.
How code is managed
- Repository (repo)
- The folder that holds your project's code plus its entire history. Usually stored on GitHub.
- Version control (Git)
- The system that records every change ever made to your code, so you can see what changed, when, and undo anything. Git is the one everyone uses.
- Commit
- One saved change with a note about what it does — a snapshot in your project's history you can always return to.
- Pull request (PR)
- A proposed batch of changes, packaged for review before it joins the main code. The natural checkpoint where changes get looked at — by people, or by tools like this one.
- Code review
- Reading a proposed change to catch problems before it ships — the practice that most separates professional teams from everyone else.
- CI (continuous integration)
- A robot that automatically builds and tests your code every time you propose a change, so broken things get caught in minutes instead of by your users.
Shipping and running
- Test
- A small program that checks part of your app works — automatically, every time anything changes. Tests are how you change code without fear.
- Deployment
- The act of putting a version of your app onto the internet. Modern tools make this a button press or fully automatic.
- Production
- The live version of your app that real people use. 'It broke in production' is why everything else on this list exists.
- Staging
- A private copy of your app used to try changes safely before they reach production.
- Environment variable
- A setting your app reads at runtime — like a database password — kept outside the code so secrets never get written into it.
- Release
- A named, decided moment of shipping: this set of changes, judged ready, goes out. Releases are decisions, not accidents.
- Rollback
- Putting the previous working version back after a bad release. Good setups make this fast and boring.
- License key
- A code proving you have the right to use a piece of paid software — how tools like this one know who you are, without a password.
Working with an AI, well
Building with AI is a skill of its own. The short version:
- Ask for one small thing at a time, specifically.
- Read what you get; ask the AI to explain anything you don't follow.
- Test after every change, not at the end.
- When it goes in circles, restart the conversation with a cleaner ask.
You know the words now
The guided path sets up Enterprise Skills in your editor and walks your first governed session — every concept above, applied for you.