WeSolve+ reads the whole document and writes the questions for you
Upload your PDF, photograph your notebook, or point the camera. WeSolve+ writes questions from that material, explains why each answer is right, reads the chapter back to you as a podcast, and remembers every item you missed until you own it.
The tool below is a small browser-only tool and it is not WeSolve+: paste a few lines and text rules turn them into cards on the spot. The real app, the one that uses AI, is behind the link above.
Process vocabulary, from your notes
This is a browser-only tool, and that is all it isIt splits the text you paste by rule, and nothing else. WeSolve+ is a different thing entirely: it reads your whole PDF with AI, writes the reasoning behind every question, speaks the chapter back to you, and remembers what you missed so it can return it. Try the real app now, free!
This tool splits the text you paste by rule and returns cards. It does not run, read or debug code, so it works on the process vocabulary you already wrote down.
Three error types, and only one announces itself
A syntax error stops the program from running at all. A runtime error appears during execution. A logic error runs cleanly and returns the wrong answer, which makes it the dangerous one and the one questions target. Being able to say which kind a described symptom implies is a recurring and very learnable mark.
Iteration is a claim about process, not a synonym for repeating
Designing, implementing, testing and returning to design is different from writing the whole thing and then fixing it. The distinction is examinable, and describing your own work in those terms is what the written portions reward. A student who says they built it and then debugged it has described the process the unit argues against.
Collaboration is assessed, which surprises people
Naming what a collaborator contributed, and what you took from their idea, is part of the work rather than a courtesy. The unit treats programming as something people do together, so an answer that presents a solo effort where there was a team is answering a different question from the one asked.
Test cases have a required shape
The ordinary case, the boundary and the case you expect to fail. Testing only the ordinary case is the most common weakness in student answers, because it is the only one that feels productive. Naming a boundary explicitly, such as an empty list or a zero, is usually worth more than adding a third normal example.
Abstraction is introduced here and used everywhere later
Abstraction means hiding detail behind a name so you can reason about the whole. A function name, a variable, a list: each one lets you stop thinking about what is inside it. Explaining what a particular abstraction hides, and why that helps, is a question shape that recurs across the entire course.
What to photograph for Creative Development
Your process notes and any code you commented at the time. Related: Precalculus Unit 1, PDF to quiz and pricing.
Sources used on this page
- College Board, AP Computer Science Principles
- Abstraction (computer science)
- Algorithm
- Binary number
- Data compression
- Active recall
- Spaced repetition
- Testing effect
- Forgetting curve
- Generation effect
- Judgment of learning
- Metacognition
- Desirable difficulty
- Distributed practice
- Formative assessment
- Flashcard
- Cloze test
- Multiple choice
- Test (assessment)
- Educational assessment
- Advanced Placement
- Curriculum
- Study skills
- Study guide
- Note-taking
- Overlearning
- Instructional scaffolding
- Item analysis
- Mastery learning
| Error | What happens | How a question describes it |
|---|---|---|
| Syntax | Does not run at all | The program will not start |
| Runtime | Stops during execution | It crashes partway through |
| Logic | Runs, wrong answer | It works but the output is wrong |
| Ordinary test | Confirms the normal path | Necessary and not sufficient |
| Boundary test | Checks the edge | Empty list, zero, maximum |
| Failing test | Confirms handling | What should it refuse to do |
What is AP CSP Unit 1?
Creative Development: program design, iterative development, collaboration, testing and debugging. Much of it is assessed in writing rather than in code.
What is the difference between a logic error and a runtime error?
A runtime error stops execution. A logic error runs cleanly and returns the wrong answer, which makes it harder to notice and more often examined.
What does iterative development actually mean?
Designing, implementing, testing and returning to design repeatedly. It is not the same as building the whole thing and then fixing it.
Why is collaboration part of the assessment?
Because the unit treats programming as something people do together. Naming what a collaborator contributed is part of the work, not a courtesy.
What makes a good set of test cases?
An ordinary case, a boundary such as an empty list or zero, and a case you expect to fail. Testing only ordinary cases is the most common weakness.
What is abstraction in this course?
Hiding detail behind a name so you can reason about the whole. Explaining what an abstraction hides, and why that helps, recurs throughout the course.
Last updated: 2026-08-11