Planning a project
Plan before you code: user stories, wireframes on paper, a list of tables and endpoints, and small steps with a done-when for each.
Transcript
Before you write code, plan. Start with user stories: sentences that say, as a who, I want what, so that why. For example: as a pet owner, I want to add my pets, so that I can see them all in one place.
Next, sketch the screens on paper: boxes for the list, the form and the buttons. This is called a wireframe. It is quick to change, which code is not.
From the sketch, list what you need. Each screen needs data, so write the table. Each action needs a request, so write the endpoints, like GET slash api slash pets.
Finally, cut the work into small steps, each with a done when. Build the smallest step that works, then the next. Three must haves first, nice to haves later.
Remember: a user story says who, what and why. A wireframe sketches the screens, a plan lists the tables and endpoints, and small steps get you there.
More in this series
1:3348How the whole app fits together
A full stack app has a front end, a back end and a database. Follow one click from the page through fetch, the Go server and the database and back, with every term from the earlier lessons.
1:1750Staying safe as a developer
Habits that keep you and others safe when you build apps: no secrets in code or Git, made-up test data, never trusting input, crediting other people's work and being kind.
1:2351Deploying an app
From localhost to the home network to the internet: what a server computer, a domain name, DNS and HTTPS do, and why public means more risk.
1:2052What to learn next
A map of next steps after the first year: front-end frameworks and TypeScript, more Go and databases, algorithms, games, security and open source, and how to keep learning safely.