What to expect
How long things take, what a good working rhythm looks like, and the parts that genuinely go wrong.
Honest expectations, including the unflattering ones.


How long things take#
| Roughly | |
|---|---|
| Creating an application | Two minutes of answering questions |
| The first build | 5–20 minutes, depending on how much you asked for |
| A small change | 1–4 minutes |
| A substantial feature | 5–15 minutes |
| Deploying to test or live | 1–3 minutes |
These are the times on a normal day. A build that has to install new packages takes longer; one that hits an error and works its way out of it takes longer again.
The rhythm that works#
Small asks beat big ones. Three messages that each change one thing produce a better result than one message with eleven requirements in it, and when something comes out wrong you know which sentence caused it.
React rather than specify. You do not have to describe the application perfectly up front. Look at what came back and say what is wrong with it. This is faster and more accurate than imagining the whole thing in advance.
Say what, not how. Salespeople should only see their own proposals is a good instruction. Add a WHERE clause on owner_id is not — and if you knew that much, you would not be here.
Be concrete about the thing that matters. "Make it look better" produces something arbitrary. "The stage column is too far right and the dates are unreadable" produces the fix you wanted.
What goes wrong#
It misunderstands. Regularly, and usually because a sentence had two readings. Say so plainly — no, I meant the owner of the proposal, not the account manager — and it corrects with the whole conversation still in mind.
A build fails. It happens. The work is still saved, the failure is explained in a sentence, and continue usually gets past it. See When a build fails.
It changes something you liked. Ask for it back, or go to an earlier version. Every build is kept, so nothing is ever actually lost.
It refuses. Some things are genuinely outside what this platform does — a different framework, a service that is not connected. It will say so rather than pretend.
What does not go wrong#
Worth knowing, because these are the fears people arrive with.
You cannot lose work by forgetting to save. Every build becomes a version automatically, including the ones that failed or that you stopped.
You cannot break the live application by building. A build changes the preview. The live copy keeps running the version you deployed until you deploy another one.
You cannot ship something broken by accident. A deployment builds the version first and only moves the address once the new copy answers. A version that does not build never replaces the one that is live.
You cannot corrupt the live data from test. Each environment has its own database. They cannot see each other.
When to ask a person#
Some things are faster to ask us than to work out:
- The application needs to talk to a system we have not connected.
- You want it in a language other than the one it came out in.
- A build has failed the same way three times.
- Something about the result is wrong in a way you cannot describe.
Ask. It is not an admission of anything.