You have not recorded evidence yet. Start with the first recommended topic, then mark the evidence you can demonstrate.
Your progress is available for this visit only because browser storage is unavailable. Keep this page open or record your evidence elsewhere.
Learn deeply
Build a durable mental model, then transfer it into a working application.
Implementation fluency
Stage purpose: Establish the vocabulary and first working mental model.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Explain the core idea and use it in a small example.
Estimated time: 70 minutes
-
Lesson · Estimated time: 35 minutes
Outcomes
- Choose interview-ready Java collections
- Avoid numeric overflow in solutions
Prerequisites: No prerequisite topics
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Java Strings & Fast Input — Carry the Java subset into strings, characters, and fast input—the daily mechanics of a timed problem.
-
Lesson · Estimated time: 35 minutes
Outcomes
- Transform strings without accidental quadratic work
- Parse input with a reusable fast-reader pattern
Prerequisites: Java for DSA
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Modular Arithmetic for DSA — Add arithmetic discipline to the same implementation toolkit before counting larger structures.
Maths for problems
Stage purpose: Connect the concepts into a repeatable problem-solving model.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Apply the model to a representative exercise without copying a recipe.
Estimated time: 75 minutes
-
Lesson · Estimated time: 35 minutes
Outcomes
- Keep modular calculations overflow-safe
- Use fast exponentiation and modular inverses
Prerequisites: Java for DSA
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Combinatorics — Counting Techniques — Use the arithmetic toolkit to make counting formulas executable instead of merely memorized.
-
Lesson · Estimated time: 40 minutes
Outcomes
- Choose permutation or combination reasoning
- Compute constrained counts safely
Prerequisites: Modular Arithmetic for DSA
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Java for DSA — Workbook — Retrieve the foundation ideas across mixed prompts before moving into specialized data structures.
Retrieval and transfer
Stage purpose: Transfer the concepts into a realistic implementation task.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Produce a small artifact that proves the decision works.
Estimated time: 45 minutes
-
Workbook · Estimated time: 45 minutes
Outcomes
- Retrieve foundation patterns without notes
- Diagnose a wrong answer from its symptom
Prerequisites: Combinatorics — Counting Techniques
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Complete this path by applying these outcomes in your own project.
Prepare for interviews
Prioritise high-frequency material, retrieve it quickly, and practise explaining it clearly.
Essential mechanics
Stage purpose: Secure the concepts that recur in most interviews.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Give a concise, accurate explanation with one concrete example.
Estimated time: 24 minutes
-
Lesson · Estimated time: 12 minutes
Outcomes
- Choose interview-ready Java collections
- Avoid numeric overflow in solutions
Prerequisites: No prerequisite topics
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Java Strings & Fast Input — Move from collection choices to the string and input patterns interviewers expect you to write quickly.
-
Lesson · Estimated time: 12 minutes
Outcomes
- Transform strings without accidental quadratic work
- Parse input with a reusable fast-reader pattern
Prerequisites: Java for DSA
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Modular Arithmetic for DSA — Follow input fluency with modular arithmetic, a common source of silent wrong answers.
Maths patterns
Stage purpose: Rehearse implementation choices that invite common follow-up questions.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Walk through a realistic API decision and defend the trade-offs.
Estimated time: 27 minutes
-
Lesson · Estimated time: 12 minutes
Outcomes
- Keep modular calculations overflow-safe
- Use fast exponentiation and modular inverses
Prerequisites: Java for DSA
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Combinatorics — Counting Techniques — Turn modular operations into a counting answer with explicit constraints and cases.
-
Lesson · Estimated time: 15 minutes
Outcomes
- Choose permutation or combination reasoning
- Compute constrained counts safely
Prerequisites: Modular Arithmetic for DSA
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Java for DSA — Workbook — Test whether the formulas survive a mixed timed set rather than a single familiar example.
Timed retrieval
Stage purpose: Combine concepts under time pressure in design and implementation prompts.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Structure a complete answer from requirements through verification.
Estimated time: 20 minutes
-
Workbook · Estimated time: 20 minutes
Outcomes
- Retrieve foundation patterns without notes
- Diagnose a wrong answer from its symptom
Prerequisites: Combinatorics — Counting Techniques
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Complete this path by applying these outcomes in your own project.