My function draws a target. It takes x and y.
It works well and I am happy with it.

My function draws a target. It takes x and y.
It works well and I am happy with it.

drawTarget(x, y, size) draws one target wherever
it is told to. The rings are drawn by a loop that
counts down from 3, and an if inside it colors a
hit target gray instead of red. It is called from
the traversal that draws all the targets, and
again to draw the one under the mouse.

drawTarget(x, y, size) draws one target wherever
it is told to. The rings are drawn by a loop that
counts down from 3, and an if inside it colors a
hit target gray instead of red. It is called from
the traversal that draws all the targets, and
again to draw the one under the mouse.

'F' → Fullscreen

Build

Open your program once, run it, then close the editor and write from what you remember. If you get stuck, open it again — but notice that you had to.

Task 1: Purpose and Use

Two short paragraphs on the documentation sheet:

• Purpose. What the program is for. Not the mechanics — why anyone would run it.
• Use. What a person does, in order, from launching it to finishing. What they press, what they see, how it ends.

Task 2: Your Procedure

The graded one. Write about the function you wrote, and cover all five:

1. Its name and its parameters, and what each parameter is for
2. What it does with them
3. What the loop inside it repeats, and how many times
4. What the decision inside it decides
5. The two places it is called from, and why each one calls it

Then paste the function itself underneath. It should be short enough to read in one go — if it is not, say so and explain which part matters.

Task 3: The Table

What is in it, what the program does with it, and what would happen if you deleted it.

If the honest answer is "not much", say that. An accurate description of a weak table is worth more than an invented description of a strong one, and it tells you exactly what to fix in Quarter 3.

Task 4: What You Cut

Three sentences:

• What you planned that is not in the program
• When you decided to drop it, and why
• What you would build first with another session

Task 5: One Bug

Describe the worst thing that went wrong while building. What you saw, what you thought it was, and what it actually was.

"What you thought it was" is the interesting part and it is the part people leave out.

Checkpoint

• Purpose and use, both written
• Your procedure described with all five points, and the code pasted
• The table described honestly, including the delete test
• What you cut, and when you decided
• One bug, including what you thought it was
• Handed in on paper at the start of the exam session

Reflection

Answer the following questions before submitting your work.

1. You wrote about your program with the editor closed. Say which part you could not remember, and what that tells you about writing code you will have to explain in May.
2. At the gallery walk you saw somebody else's program do something yours did not. Describe it, and say what you think they had to know to build it.
3. This quarter started with a program that printed one line. Name the single idea from the last twenty-five sessions that made the biggest difference to what you can build, and say why that one.

Submit

Hand the documentation sheet in on paper at the start of the exam session. Do not email it — you will not have a computer that period.

Response Complete