Ready Set Code!

⚠️ 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

• 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.
  • Your tasks should reflect the decisions you have made about how you will implement things (i.e., they are specific and detailed).
  • 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.
  • Make sure you have a .gitignore file! You can get one that is specific to your project at gitignore.io.
• You are clear on the git and GitHub workflow for your team.
• 🚨 Make sure you are using django-environ and a .env file. This will be especially important for secret keys and sensitive info, like AWS credentials. DON’T COMMIT YOUR SECRET KEYS!
• 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

• Make sure you are using Postgres and not SQLite.
• Models! What models will you need?
  • What fields belong on those models? Use the Django Model Field Reference.
  • What relationships exist between your models? (one-to-many, many-to-many?)
    • Consider using the CRC model to help guide your discussions.
    • You should create a 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 request?
  • 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?
• Deploy early and often. Who will deploy? Make sure more than one person on your team has the ability to do this.

✅ Checklist for the front-end

• Have you mapped out a user flow through your app?
• Wireframes for each interface the user will see
  • With backend, can you say what URL corresponds to each page or interface the user sees?
  • If using React Router (with a separate front-end application), what urls do you need?
• 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 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, Tachyons)? What is the general look and feel of your app?
  • Start to think about UI/UX and design
• Deploy early and often. Who will deploy? Make sure more than one person on your team has the ability to do this.

Reminders

• Standup starts Monday 8/09 @9:30 am or @9:45 am (check your email for a cal invite)
• First check-in Monday 8/09 @your assigned time (check your email for a cal invite)

Standup and check-ins will use this Zoom classroom.