Required Entry Format
Use this structure for labs, projects, AP Classroom corrections, and major JuiceMind or CSAwesome assignments.
Each entry should include
- Title and date: Name the assignment, lesson, or problem set.
- Goal: State what the program or concept was supposed to do.
- Key concepts: Identify the Java ideas used, such as conditionals, loops, classes, methods, arrays, or strings.
- Code evidence: Include a small code segment or describe the exact section you worked on.
- Testing: Record inputs, expected outputs, actual outputs, and what you changed.
- Reflection: Explain one mistake, one insight, and one next step.
Quality expectations
- Write in complete thoughts. Bullet points are fine when they are specific.
- Do not paste entire programs unless asked. Choose the part that shows your thinking.
- Use vocabulary from class accurately: object, method, parameter, return value, loop body, condition, constructor, instance variable.
- When correcting an error, explain the cause, not just the fixed answer.
- End each entry with what you would try first if you saw a similar problem again.
Journal habit: Good programmers keep track of decisions. A strong entry shows how you moved from confusion to evidence, from evidence to revision, and from revision to understanding.