Daily Plan
Plan for this week of the Binary Logic project
Week 0
- Monday
- Create groups of 4 and assign roles
- Tuesday
- Discuss plans and goals for the project
- The project should only be frontend and use some sort of binary
- Wednesday
- Start researching how to use binary
- Thursday
- Start coding binary into projct
- Friday
- Have a tangible frontend
Monday pick team of 4.
Setup your GitHub Pages, every project should be working from NightHawk Pages theme. This will be frontend project and we will be learning SASS.
Tri 2 seed awards…
below 93% receives 2.7/3
93% and above receives 3 points
Plan features in Teams need to be assigned 2 by 2. All live review discussions will be in Teams of 4, but features will be discussed in pairs (Innovation, Design, Feature Dev, Integration, Testing, Final).
Assignment of next round of Student Teaching. A couple of topics for PBL might be included, depending on need. Eyes, Nose, Finger, Toes, (you are the Pulse, Body of the class builds content for everyone).
Tuesday Tech Talk, GitHub Page and SASS overview, Binary Logic requirements overview
Thursday/Friday Q&A, Binary Feature Discussion table by table. At this point there should be Innovation and Design.
Week 1
M - Work Day, Internet teaching teacher/student teachers preview Tu - 4.1 The Internet W - Work Day, Routing and Computing teacher/student teachers preview Th - 4.2 Routing and 4.3 Computing F - Binary Logic Code reviews (4 person team, 3 to 5 minutes)
Important Notes slides:
Remember project focus is on Binary. Confusing usage of review ticket, a review requires demonstration of tangibles. Remember materials are required to be in ONE PLACE, your GitHub. Usage of GitHub Issues, GitHub Pages, or GitHub Repo are acceptable locations. Do not require Teacher to access information using an account. Graders need to. give productive comments (1 or 2 positives and 1 or 2 growth statements would be a minimum. As a positive, there is one terrific example from Hanlun, Lakshanya, Matthew, Aditya, Trevor. Only issue with there could be solved by adding Utterance comment to page.