Skip to the content.

Final Review

MCQ reflection and reflection on trimester

MCQ

MCQscore

MCQscore

MCQunits

MCQpractice

MCQ Focus Areas

  1. Arrays and ArrayLists:
    • review reading and modifying data collections (arrays, objects, etc..)
    • Identify off-by-one and null pointer issues.
  2. Nested Loops and Conditionals:
    • Focus on how loop variables change and affect program flow
    • Practice tracing and predicting outputs (read algorthms and then them to test for accuracy!)
  3. Debugging and Tracing:
    • Work on spotting logic and syntax errors
    • review diffrent types of errors (compiling, overflow, etc…)

Review Questions

Q1

key Concept: A static variable belongs to the class itself, not individual objects. Every time the constructor with count++ runs, that one shared variable increases for all objects not just one!

Focus Practice:

  • Differentiate between instance and static variables

  • Practice tracing how many times a static field updates within multiple constructors.


Q2

Key Concept: The inner loop compares every pair of strings. If two words have the same string length, it updates result = k. The last match in the array is “black” (index 3) and “brown” (index 5), so result becomes 5.

Focus Practice:

  • Practice tracing nested loops using pencil and paper, writing down j, k, and updates to variables to follow the output of the function better (they give paper on the AP exam!)

  • Focus on when updates occur and whether they overwrite previous values or not


Q3

Key Concept: The substring (start, end) method returns part of a string starting at start (inclusive) and stopping just before end (exclusive).

If you only give one parameter like substring(4), it means “start at index 4 and go to the end.” When you concatenate substrings, you can rearrange or rebuild parts of a string in a new order.

Focus Practice:

  • practice predicting the output of functions before running them to gain more exposure

  • Practice rearanging substrings to create new words

Example: “HELLO”.substring(1, 4) → “ELL”



How N@TM Went

Project

Feedback

TeamPic Spectators

Good

  • Felt very confident and natural presenting and answering questions

  • We had a lot of engagments from the audience especially for our fun features like generating the resume and practicing the interview

  • the technical features ran smoothly and we had no technical difficultues with backend or the data saving

Bad

  • Sometimes the audience would get board neer the begining of the lesson which is more geared towards inputing the data that is used towards the more fun features at the end

  • the design felt a bit unfinished, the sleak cohesive styling worked but it didnt have a lot of personality

  • additionally the sprite felt out of place with a white background and was a bit small and hard to see without zooming in or pointing it out (we created the video by hand)

Future Improvment

  • Add more layout options for the resume generator

  • Add more structure to the lesson so its easy to follow without someone guiding you through it (especially more structure to the interview bot thing)

  • polish the astetic and style of the page so it fits more with the contents and is less bleak (but also not to messy and unmaintainable)



Analytics

CommitsTotal

Open Coding anayltics page

Insights

Commits on NEW grinders fork

Insights2

Commits on OLD grinders fork



Ideas For Next Project!

Game design

  • use of sprites (with me soni and avika having played around with sprites in the last trimester)

  • creating a storyline dependent on the decisions the user makes, using machine learinng to create the next storyline based on the previous actions of the users

  • utalizing more modalities with voice lines, sprites, machine learning, AI addition, and posibly datasets from other games and user tests

  • like this project we can sprite up the features among the groups in the class to create game together, to both learn to incorperate teamwork, and to give everyone time to perfect their features

  • This could also be a comparrison to the games we created in CSSE, to show the improvment from CSSE into CSA in the sophistication of our code and game!

I want to focus on learning what users prefer dependent on the actions they make and how I can use that to my advantage when creating websites, games, and lessons, inorder to maximize engagment and user intrest