📓 Wednesday Schedule and Expectations
Welcome to your third day of Epicodus! Today's schedule is fairly similar to yesterday.
Schedule​
Once again, times are approximate.
8:00 – 8:30 am: Cohort Scrum with your Instructor
We'll start class with a Cohort Scrum meeting, with your instructor and your cohort. This is the usual Scrum that you'll take part in every class session for the rest of the program, and we'll meet using the same Google Meet link.
Cohort Scrum is a time for your instructor(s) to make announcements, cover certain topics from the curriculum, and for you to ask questions. These Scrums can vary in length depending on what needs to be discussed. If you are having any problems accessing the meeting, reach out to an instructor.
After this week, Cohort Scrums on weekdays will start at 8:15 pm and will be a shorter length — about 15 to 20 minutes. We have a limited amount of time during weekday classes so we'll keep meetings short to have more time for hands-on coding.
8:30 am: Join Dev Team
After Cohort Scrum, you'll join your dev team. You'll have the same dev team for the entire course section. If you are having any issues with members of your dev team, please reach out to an instructor.
After this week, you will start every class session with your Dev Team Scrum meeting. On weekdays, Dev Team Scrum starts at 8:00 am.
8:30 – 8:55 am: Dev Team Scrum
Except on the very first week of class, you'll start everyday with a meeting with your dev team. We call this meeting "Dev Team Scrum".
The first thing you should do during your Dev Team Scrum is sign in to the Epicodus attendance system. You should also remind your fellow dev team members to do this as well so that no one forgets!
Next, make sure that everyone is present for the Dev Team Scrum:
- If you are an online student, this includes conducting a connectivity debugging session. Is everyone able to access the voice channel in Discord? If not, take a few minutes to make sure everyone is taking part. Remember, if you have recurring issues, reach out to an instructor. When everyone is connected, you can start your brief group check-in.
- If you are studying in person, take the time to make sure that everyone who is in your dev team and present for class is together before start your brief group check-in.
As a reminder, Dev Team Scrum includes a brief group check-in to talk about anything that came up during the last class session — such as things you've learned or things that you find exciting or frustrating. This is also a great time to ask each other questions about any content that you might find confusing. As covered in the lesson about working with a dev team, in about 15 minutes, each student in the dev team should answer these 3 questions:
- What did you work on in the last class session or over the weekend?
- What are you working on today?
- What blocks do you have? What is standing in your way?
Once everyone has had a chance to speak, the next step is to find a pair from within your Dev Team and then begin pair programming. If there is an odd number of people in your dev team, there will be one group of three.
8:55 – 11:40 am: Pair Programming
11:40 – 12:00 pm: End of Day Cohort Scrum
We'll meet briefly before the end of class to talk about how the day went.
Third Day Expectations​
We'll be covering the following key coding concepts today. These concepts will all be required for this section's independent project. Just like yesterday, these are concepts you'll be using throughout the program. Don't worry if all these concepts aren't clear by the end of today — you'll be practicing them over and over not just this week but throughout your time at Epicodus.
The following are brand-new concepts that you'll get lots of opportunity to practice further:
- Git as a version control system, and Git commands.
- GitHub and Remote Repositories
- How to use Git and GitHub in your workflow while coding
You will need to be able to use all of the above concepts for this course section's independent project — and for future independent projects as well. Independent project prompts are released on Friday at the end of the course section and due the following Monday.
Take note: on short weeks, daily expectations change, and you may cover more or less content on a given class day.