AP CSP Create performance task guide

1. No comments, anywhere. The handouts say your code segments "should not include any comments", and that course content or comments in the PPR lead to a score of 0 on the Create performance task, including the written responses.
2. Readable text. At least 10-point font. The tip sheet adds: "The use of 12-point font is even better."
3. Capture at 100 percent. The FAQ says to take captures while the application displays at 100%, and the tip sheet warns against zooming out and enlarging later, which makes text blurry.
4. Split long code. "Each image box allows up to three screen captures." For a long segment, capture it in sections and upload them in order.
5. Handle wide code. Shorten long lines with variables if you can. If not, the tip sheet says to rotate the captures 90 degrees and "always rotate them in the same direction".
6. Print it once. Saving the PPR in the Digital Portfolio creates a PDF; print it and read it before submitting as final, because that printout is close to what you will have on exam day.

Sources: AP CSP Personalized Project Reference Tip Sheet and the AP CSP Student Handouts, read 17 October 2026. The exam-day prompts change every year.

# Practice only: never submit sample code
def count_long_words(words, min_length):
    total = 0
    for word in words:
        if len(word) >= min_length:
            total = total + 1
    return total

spelling_list = ["orbit", "comet", "nebula", "star", "galaxy"]
print(count_long_words(spelling_list, 6))
print(count_long_words(spelling_list, 0))

Write your own answers before reading ours, in two or three sentences each. Then do the same exercise, out loud, on a practice project your teacher sets. For a broader look at the two AP computer science courses, see AP CSP or AP CSA first.