# Unit Planning (The HackMD Title) #### CodePath | Android | Spring 2020 ## Header 1 (this is an example of a header) What's up Android fam. We can see the virtual :bread: in the horizon, so now let's get it. Just as a reminder, we should think of ourselves as ***experience engineers***. We are **engineering** the students' **experience** with Android concepts and tools (but don't put that on your LinkedIn, it's not as good as Technical Program Manager or Director). ## Office Hour & Quiz Google Forms: We should try to create a google form giving students options to attend various office hours. I think we should each pick 30 mins to 2 hours max of our time to have live zoom sessions with the students. During this time, if nobody shows up to your zoom office hours, it would be wise to work on codepath-related things so that you're in that same frame of mind if students show up. ## Unit Video Topics Idea: Here is a sequence of ideas we could consider when we're creating the first video for Unit 1. ### Unit 1 #### Course Logistics and Resources 1. Show them the [course github repo](https://github.com/CodePath-at-UCI/android-course) and explain that it'll have updates with resources. 2. We should not go over THIS [syllabus](https://courses.codepath.org/snippets/android_university/syllabus_spring_2020) as UCI's Android structure is different and CodePath's default syllabus will confuse students in our course. We need to create a **brief**, new syllabus for our course outlining the following so the students can understand: - how the grading system works, - how attendance works, and why it's important to have good attendance [(refer to CodePAth syllabus for WHY it's important)](https://courses.codepath.org/snippets/android_university/syllabus_spring_2020) - the number of units the course has - and what topics are covered in each unit. 3. Explain how attendance works (quizzes on saturday asking simple questions from the video. I.E. 60% or higher = credit for attendance) 4. Remind them about slack, and show them how to use the [discussion system](http://discussions.codepath.com/sessions/login) #### Unit 1 content 6. Slightly modify the [slides for unit 1](https://drive.google.com/drive/u/0/folders/1jd3ytLEs_TIM8ZJWbpHFyITg1znIs3iC), and then go over the slides to help students learn about the concepts and ideas 7. Do a coding demo with the lab to put the concepts into practice. Show your screen and explain out loud what you're doing, why you're doing it, and (ideally) what each line of code means. 8. Remind students about the next assignment and it's due date. ##### **Analysis** - It would be a good idea to **divide the workload amongst yourselves and work together** to accomplish these steps. - Steps 0 through 3 would be easier and faster to do than steps 5 through 7 - We can record the video with zoom, and choose the option to have it uploaded to the cloud, since that's probably easier and quicker. - Then we could put that link on the course github repo ### Unit 2: 1. Go over any announcements 2. Do a recap from last week (2 main choices) 1. Lightly reiterate the coures github repo, syllabus, attendance quizzes, slack, discussion forums, and THEN unit 1 topics) 2. Jump straight into unit 1 slide topics/concepts, and then remind them what we did in the previous lab 3. Start unit 2 slides while explaining topics and concepts 4. Do the coding demo for that unit's lab 5. Remind students about the next assignment and it's due date ##### **Analysis** This might be a good format to follow when we create videos. Please give me your thoughts on this process and if there's any part of it you'd like to change.