Essay
What "Built in a Weekend" Leaves Out
A weekend can produce a draft. It does not produce a product other people should rely on.
The day-job essay makes the useful claim: if you know the work, a free chat tool can help you start. The inflated claim, “shipped in a few evenings, no code, customers waiting”, is what this page leaves out.
You can have
One problem, one sample output, and a list of what the draft gets wrong.
You do not have
Customers, a backup, today's prices, or anyone who should trust it overnight.
What a weekend can honestly hold
Section titled “What a weekend can honestly hold”One problem you have met more than ten times. Not a company.
By Sunday night you can have:
- A paragraph that describes the problem in the words you actually use.
- One sample output: a quote, a checklist, a parent note, a handover.
- A short list of where the draft is wrong. You will know. That knowledge is the expertise.
That package is worth having. It is a brief for a tool. It is not the tool, and it is not a business.
What the weekend does not include
Section titled “What the weekend does not include”- People paying you.
- A login, a backup, and a way to undo a mistake.
- Yesterday’s prices, today’s stock, or a patient’s real chart.
- Someone else trusting it while you sleep.
Free tiers are enough to draft. They are not free on a phone plan, and they are not a hosting company. If the draft needs private data, keep that data out. The rule is in what never to paste.
A finish line you can keep
Section titled “A finish line you can keep”Stop when you can show the sample to a colleague and they can say “that is the job” or “you missed this step”. Write down the missed step. Do not spend the last hour adding a logo.
If you still want to build after that, you are starting a different project, with a clearer brief than you had on Friday. That is the point of the weekend.
Discussion
View all discussions on GitHub