DTR
Basically open all the time, take it day by day. No set cutoff times.
Teach other Rails, React, JS etc. Git Workflow Git Rebasing
*** Squash Commits ***
GH Projects
We will be using conveyer belt
Daily! Before project.
*** Project Notes ***
Active Records - ORM That we will use for database queries Scheduler - Keep in mind.
-
User stories are complete
-
What went well? Covered all bases, fun but productive conversations in our retros and stand ups. We all feel comfortable with what our functionality will be, what the 'user flow' will be, and how we can go about beginning to code this.
-
What could be improved? It feels like we should be further along - but it just feels like that. We can adapt to the pace of the project. We can't control the pace.
-
What do you want to want to commit to change or improve during the next sprint? Cody: I would like to take the time to go back and review code written every day to help solidify my understanding. Everyone: Encourage asking for help/questions. Helps us learn by teaching.
-
What should the team start doing? When not pairing & writing code, take extra time to walk through all the code that has been written.
-
What should the team stop doing? Stop not coding
-
What should team continue doing? Continue the quality open communication. Keep the focus on the process (taking time to review code) not worry too much about busting out a ton of code but maticulously planning before we code.