Code the Dream Labs Logo

Code The Dream School

Main hub for class materials for Code the Dream’s classes

SPRINT 2: Building a Front-End UI, a working API, and Deploying some code

Learn to fix problems when your code overlaps or conflicts with others’.

Activities

Full-Stack

  • At your first week Sprint 2 full-stack meeting: continue using the “standup” format:
    • What have I been working on this week?
    • What will I be working on (or continuing) next?
    • What issues are blocking me?
    • Front and Back mini-teams discuss with each other how merge conflict processing went for your team
    • Front and Back mini-teams give a summary/debriefing of the meeting(s) you had with your ‘end’ of the project
  • At your second week Sprint 2 full-stack meeting: continue using the “standup” format:
    • What have I been working on this week?
    • What will I be working on (or continuing) next?
    • What issues are blocking me?
    • Front and Back mini-teams discuss with each other how merge conflict processing went for your team
    • Front and Back mini-teams give a summary/debriefing of the meeting(s) you had with your ‘end’ of the project

Back-End

  • Design and Build an API with CRUD capabilities 
  • Seed database
  • Test routes with Postman
  • Determine if front-end team will use deployed API or use local instance
  • Continue working on your tickets within your respective repos, taking care to work in small chunks, commit your code often, and be mindful of the work your teammates are doing so you know which files might overlap.
  • Once you have completed a ticket and your code is working well, make a Pull Request so that it can be reviewed and merged into the project’s codebase (review the GitHub Guides article for a refresher if needed).
  • At your weekly back-end and front-end meetings, work on resolving merge conflicts with your teammates.
    • Review files together to determine what the code is doing, what should be kept, and what order it needs to be in.
    • Make plans to pair program or restructure who is working on what (and when) if conflicts are anticipated to be unmanageable.
    • Draw on your Project Lead’s expertise to help you resolve these things, and get comfortable with how to communicate with a teammate during this process.

Front-End

  • Design and hard code your UI, Page Views, and Components
  • Use test data arrays and objects based on the schema created in first sprint by the backend to render data.
  • Continue working on your tickets within your respective repos, taking care to work in small chunks, commit your code often, and be mindful of the work your teammates are doing so you know which files might overlap.
  • Once you have completed a ticket and your code is working well, make a Pull Request so that it can be reviewed and merged into the project’s codebase (review the GitHub Guides article for a refresher if needed).
  • At your weekly back-end and front-end meetings, work on resolving merge conflicts with your teammates.
    • Review files together to determine what the code is doing, what should be kept, and what order it needs to be in.
    • Make plans to pair program or restructure who is working on what (and when) if conflicts are anticipated to be unmanageable.
    • Draw on your Project Lead’s expertise to help you resolve these things, and get comfortable with how to communicate with a teammate during this process.

__________________________________________________________

Additional Resources