Week 0 HACKS | Collaboration

**Collaboration**

Pair Programming

  • Feature Considerations for Project
    • Final Project and Blog Requirements
      • A home or fun zone for your blog, also a unique idea(s)
      • Educational zones that capture every key learning objective
      • About Me, consider personal privacy issues as this will be public
  • Project Technicals
    • Managing PBL Requirement for Project (Issues, Scrum Board)
    • CSSE, CSP, CSA. Use of “JavaScript, HTML, CSS”. Frontend or Presentation development.
    • CSP. Use of “Python Functions and Classes” in backend.
    • CSA. Use of “Java Classes and OOP” in backend.
    • Data Structures. The exchange between frontend and backend: Backend could be Data Frames from Pandas, “SQL” or “MongoDB” databases, etc.

Hacks

  • [ x ] Establish PBL and Comp Sci attitude; often called an Agile Mindset or Growth Mindset.

Changes and mistakes are part of the process and they will not be the end.

  • [ x ] Watch a video How I Would Learn To Code
  • [ x ] Attitude. An Agile/Growth mindset is not knowing the answer, making lots of mistakes and performing iteration. A successful grade is dependent on making mistakes, research, asking questions, and continual iteration.
  • [ x ] Requirement. Please bring a personal laptop or Chromebook to class daily. The Internet, ChatGPT, and AP Classroom web site will be considered a text book.

  • [ x ] Requirements. Everything will be distributed electronically. All code you develop will be delivered to the Cloud. No paper!

  • [ x ] Grading guidelines. There will be key technical objectives which will require producing tangibles aka tangible artifacts. Essentially, it is impossible to be late with work if you work consistently attend class, work in class and turn in progressive tangibles each week. Thus, failure to have work will result in point deduction. Additionally, late work must be defended in office hours and will receive 10% deduction.
    • [ x ] High “A” is very tough to achieve, something beyond the given tangible requirements. Something that exhibits an unforced desire to learn and Code/Code/Code. This grade is required to earn a Teacher recommendation.
    • [ x ] Low “A” is consistency in producing tangibles toward Team Project and Individual GH Page according to Issues and Scrum Board plans. Plans must be consistent with key objectives and technicals.
    • [ x ] “B” is having flaws in consistency or tangible shortcomings, but mostly on track. A flaw would be mostly working code, attempts, but incomplete.
    • [ x ] “C” is a lack consistent effort, lacking tangibles. Lack of producing working Code.
    • [ x ] Below “C” is composed of Slash/Slash/Slash offenses. Lack of attendance, disruptive behaviors, using phone inappropriately, doing work from other classes during CompSci class time, paper visible in class, and turning in tangibles that you can’t represent in live review.
    • [ x ] Zero is a result of plagiarism. The Teachers will likely miss first offenses of plagiarism, thus any offense will result in an inquiry on previous work. Remember this is an effort based class.