Ready Set Code! 🚥
Posted on Jun 16th, 2022
⚠️ Before you start writing code
Today should be used for finalizing planning and doing research on data, technology, and tools you might need.
The following checklists will help you know when you are ready to start writing code.
✅ Checklist for the whole team, before you write code
- Every team member is clear on your MVP, and you know exactly what you are building.
- You have added user stories and tasks (at minimum, for MVP) to your Trello board backlog, and you have first tasks queued in Current Sprint.
- Your tasks should reflect the decisions you have made about how you will implement features (i.e., they are specific and detailed enough that you know where to start).
- Make sure your tasks are labeled according to what responsibilities belong to the front end or back end.
- You have created a team organization on GitHub and added every team member.
- You have created your project repo or repos on GitHub and made sure everyone is added as a collaborator.
- Make sure you have a
.gitignorefile! You can get one that is specific to your project at gitignore.io.
- Make sure you have a
- You are clear on the Git and GitHub workflow for your team.
- Consider appointing a rotating team lead who can be responsible for running standup, leading at check-in, and looking after the Trello board.
✅ Checklist for the back-end
- Models! How will you represent the nouns your project needs?
- What fields belong on those models? Use the Django Model Field Reference.
- What relationships exist between the models? (one-to-many, many-to-many?)
- Consider using the CRC model to help guide your discussions.
- You should create an ER (entity relationship) diagram for your models to map relationships. This may change as you work, but you should have a good plan to start with.
- What URLs will the front end need?
- What data will the front end rely on the back end for?
- Are you returning HTML? -> What templates does the front end need, and who will make those?
- Are you returning JSON? -> How will you structure your data?
- 🚨 Make sure you are using
django-environand a.envfile. This will be especially important for secret keys and sensitive info, like AWS credentials. DON’T COMMIT YOUR SECRET KEYS! - Make sure you are using Postgres and not SQLite.
- Deploy early and often.
- Will you be deploying manually?
- When will you deploy?
- Make sure more than one person on your team has the ability to do this.
- Make sure that the main branch on GitHub is also up to date.
- Will you be deploying manually?
✅ Checklist for the front-end
- Have you mapped out a user flow through your app?
- Wireframes for each interface the user will see
- What URL corresponds to each page or interface the user sees? (with or without React Router)
- What data will you need on each page or interface? Where is it coming from?
- What requests will you need to make from the front end?
- Are you making forms? Discuss data with the backend.
- What assets (e.g. images, logos) will you need?
- General strategy for CSS and design so that you can budget time for it.
- Are you using a CSS library (e.g. Material UI, Bulma)? What is the general look and feel of your app?
- Start to think about UI/UX and design
- Deploy early and often.
- Make sure that more than one person on your team has access to the Netlify account where your app lives.
Reminders
- Standups start Tuesday 06/21 @9:30 am (check your email for a cal invite for your team’s time)
- Check-ins start Tuesday 06/21 @10:30 am (check your email for a cal invite for your team’s time)
- Please be on time for standup and check-ins.
Standup and check-ins will use your regular Zoom classroom.