-Having a good understanding of the layout. Better understanding of localStorage, really use this project to grow into it. -Trying to work with the code on seperate branches to bring more ideas to the team. -I need consistent communication with the gorup. Specificaly, if we are going to commit || push a feature, will let the group know ahead of time to avoid merge conflicts.
-Continue to develop git workflow, especially due to us needing to be working remote. Getting more reps with javascript.
-Overall, if we receive advanced beginner or proficient we want to make sure we are all comfortable with that.
-Being able to talk about javascript more fluently and feeling confident during the eval.
-Plan our project worktime out to give the team a cushion right before we turn in the project.
-Time managinging for all the projects going on.
-Use evening times for the group project and pairing.
-12/22-12/23 Keep up with the break times: ten minutes every hour, 30 minutes for lunch.
-Kim: Lover of wisdom, Order(Specialist), Self-examiner. -Sally: Flexibility/Adaptability, Persistence, Self-confident. -Kayla: Empathy(‘I get you’), Resiliency(Can Do Attitude), Practical(Team Player)
-Bring up the hard times, don’t suffer in silence. -Be open about the obstacles. Pairing with upper mods. Regularly checking in. -if something comes up unexpectedly in scheduling just give a quick update through slack or textmsg.
Schedule Expectations: When are we available to work together and individually? What constraints do we have?
-Evenings for the work time as a group.
Saturday/Sunday 10:30am-4:30pm
-Revisit DTR and work on remote schedules. -Kayla, Sally, Kim - 25th not working
-Everyday, especially during our evening times. -Exchange numbers to also have that line of communication. -Slack
-Javascript for Kim and Kayla. -Local storage for all of us. -Git
-We are planning on side by side coding for the 1st week, so we want to revisit on Sunday and DTR to make the remote work more fluid.
-Feel more in charge of writing functions and being comfortable with them.
-Writing dry html and css for future functionality.
-Git workflow and communication is going to be key. Have very few merge conflicts. -Plan a 5 min checkin before class. So we can prepare to dive into project later in the day.
-Keep the dialogue open, be honest. -Stay positive and celebrate things. -Bring more of the PD session into our communication practice: celebrate our wins, talk about things that didn't work and things we could change.
-Work off a word document Sally created to keep track of tasks, slack for communication.
-HTML and CSS Push to GitHub
Kim: -Media queries, wants to try to get the show-more show-less function working. Sally: -Refactor code to style guide Kayla: -I will start README, then the on the 2nd we will finalize the README file. -Style Cards to be fixed width and height