Staying 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.
Try it
- Developer safety checklist – Tick the habits that keep you and other people safe when you build and share an app.
Transcript
Secrets, like passwords and keys, never go in your code or in Git. Keep them in a file that Git ignores. If a secret ever leaks, change it right away.
Use made up data when you test and when you show your work. Never put the real names, photos, addresses or school details of yourself or other people into a project.
Never trust input. Check what visitors send, and use placeholders for the database, so that a visitor can never change what your code does.
Respect other people's work. Check the licence before you copy code, and give credit. And be kind in comments and messages, just as you would in person.
Remember: keep secrets out of Git, use made up data, never trust input, give credit, and be kind.
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:2549Planning 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.
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.