Describing what the program does instead of how the algorithm works
The rubric for the algorithm row requires you to explain the logic of a specific algorithm you wrote, including how sequencing, selection, or iteration operates within it. Saying 'my program sorts a list and displays the result' does not earn this point. You must explain the steps of the algorithm itself.
Using a built-in function as your algorithm
Pointing to a built-in sort, search, or filter function and calling it your algorithm does not satisfy the rubric. The algorithm must be one you wrote. If your program relies heavily on built-in functions, identify a conditional or loop you authored and explain that instead.
Forgetting to explain the complexity argument for your list
Many students correctly identify a list and describe what it stores but stop there. The rubric requires you to explain how using the list manages complexity, meaning you need to argue why the list makes your program simpler or more scalable than not using it would be.
Misaligning the video and the written response
If your video shows one feature of your program but your written response describes a different feature, scoring readers will notice. Choose one specific feature, demonstrate it in the video, and write about that same feature in your response.
Running out of time on Section I code-trace questions
Code-trace questions that require stepping through nested loops or conditionals can take 3 to 5 minutes if you try to hold everything in your head. Write out variable states on scratch paper and move on if a question is taking too long. Flag it and return rather than letting it consume time from easier questions.