Lesson Weekend

After many years of teaching thousands of students, we know that one of the most important parts of our classes is the structure we provide. When working online from home, this structure is just as important as in-person, maybe even more so! That's why while you are a remote student at Epicodus, you are expected to pair remotely, spend your day coding, take part in all stand ups, and participate in communication on the Discord server for your class as needed.

Your attendance is based on the following:

  • Did you submit your work at the end of the day? Did your project reflect a full day of work?
  • Did you pair remotely? Were you present all day and did you participate in coding with your pair?
  • Were you available in stand up and did you communicate with other students throughout the day as needed?

Here's how Epicodus will evaluate your attendance:

  • At the end of each day, you and your pair will each submit a link to the work you did that day. All students will use Github to save and store code. We will cover this requirement moment in a moment.
  • Epicodus instructors will do spot checks to ensure that all students are pairing. If you are not pair programming on Discord, you may be marked absent even if you turn in work at the end of the day. If for some reason you are not able to pair on Discord, please check in with your instructor.
  • Students will occasionally be expected to take part in student-led stand ups - or respond to questions or announcements on Discord. Not taking part may result in your attendance being adjusted.

As long you turn in your work daily, pair, and participate in class, attendance will not be an issue. Your teacher may adjust your attendance at their discretion. Based on your project's commit history and other expectations, you may be marked On Time, Absent, Tardy, or Left Early. A quick reminder: an absence counts as a full missed day while a tardy or left early counts as half of a day. Your goal is to be "On Time" every day - though please note that Epicodus provides a generous and flexible attendance policy.

Submitting Work

The primary way your attendance is evaluated is through your project's commit history. A commit saves your code and records the current state of your project. Committing code is a very common part of a developer's workflow. You'll learn more about Github (the service we use) and commits on the first day of class. Even if the concept seems a bit mysterious at first, committing your work will soon become second nature.

At the end of each day, you and your pair will submit links to the GitHub repositories you worked on that day. If you fail to turn in your work, or if the work you turn in doesn't reflect a full day of work, your attendance will be adjusted accordingly.

Your project should have a strong Git commit history showing 8 hours of work between 8 and 5. You will be expected to have at least 8 commits over the course of the day. More is better! Your commit history should also be spread out over the day - at least one per hour (outside of lunch) is expected.

If for some reason you have issues submitting your work or your commit history is lost, check in with your instructor immediately.

To submit your work, you'll log in to Epicenter at the end of the day and then click on your current course. (You need to be in the course to access the form.) You will see a form at the top of the page with a form field that says "Your GitHub repo(s) for the day (separated by commas)."

Form for submitting daily repos.

Submit links to each repo you worked on that day, make sure that you put a comma between each link. Then click the "Submit" button.

If you click on the "View past daily submissions" link (shown in the image above), you'll be taken to a page that has a table with all of your daily submissions for that course.

Daily submissions will show up in a table.

The image above shows how the table looks before you've made any submissions. Your daily submissions will be added ot this table.

Your code should have a README that includes a brief summary of what you accomplished and any issues you ran into (a paragraph is fine). You'll learn more about writing READMEs on the first day of class.

Attending Standup

It is also required to attend all standups. Crucial information is often shared during standup and we don't want you to miss any of it! However, we are aware that some students may have issues with their technology that make it more difficult to take part in video standup. In order to take part in video standup each day, we recommend the following:

  • Best option: Your computer has a working camera and access to consistent internet. If your internet is inconsistent, try using a wired ethernet condition or moving your computer closer to the router.

  • Backup option: If you are having issues with connectivity or don't have a camera, you can use your phone instead. Download the Google Hangouts application on your phone and connect to video standups via the application.

  • If neither of the above work, please contact your instructor.

Lesson 8 of 12
Last updated August 14, 2020