TechNoviceTools — AP Developer Studio — Course 03
APCS Java Dojo
“Wax On. Wax Off. Compile. Debug. Repeat.”
Java fundamentals you need to know cold.
Not memorized like a list — internalized like a motor pattern.
Because the AP exam doesn’t give you time to reason from first principles.
The Dojo at TNT
In The Karate Kid, Daniel LaRusso showed up to train and was handed a bucket of wax and a sponge. What looked like free labor was secretly karate — each circular motion encoding a defensive block into muscle memory before Daniel’s conscious mind knew what was happening. He discovered this only when Miyagi threw a punch and Daniel’s arm moved on its own.
The AP Computer Science A exam works the same way. When you see arr.length in a free-response question, you need your hand to write list.size() for an ArrayList automatically — not after a moment of hesitation. When a multiple-choice question turns on the difference between str.length() and arr.length, you need that distinction to live in your fingers, not just your notes.
The APCS Java Dojo is a collection of kata — focused, complete review sheets for each major Java concept area that appears on the APCS-A exam and in AP Developer Studio coursework. Each kata covers one concept area: its syntax, its gotchas, its most common exam patterns, and the specific distinctions that separate a 3 from a 5.
The goal is not to read them once. The goal is to drill them, revisit them before each exam, and return to them until your responses are reflexive. That’s what muscle memory means in code.
Your move: Don’t just read a kata page. Close it, open your IDE, and try to recall the key patterns from memory. What did you get right? What did you have to look up? The gap between those two things is exactly what you should drill next. That gap is the punch. The kata is the block.
The APCS Dojo was built entirely through human-AI collaboration — every prompt recorded, every decision documented, and yes, TTG’s own prompts critiqued and graded alongside the concept explanations. If you want to see what productive SPARK prompting looks like from the inside — unedited, real collaboration from concept to live venue — the Development Chat Log is required reading.
Read the Development Chat Log →
One concept area per kata. Each sheet is complete, focused, and designed to be revisited — not just read once and filed. Tables, code examples, gotcha warnings, and the specific distinctions that appear on exams.
The AP exam doesn’t reward knowing something vaguely. It rewards knowing it cold. The Dojo builds the kind of knowledge that arrives before conscious thought — the block that happens before you decide to block.
S.P.A.R.K. rhythm to use with each kata:
Set a goal →
Prompt AI →
Analyze →
Refine →
Know & Share
Every kata is anchored in the APCS-A subset — the concepts, classes, and methods the College Board actually tests. Where a topic goes deeper than the exam requires, that’s noted so you can decide how far to drill.
Mr. Miyagi didn’t apologize for making Daniel wax hundreds of cars. The reps are the point. Each kata is worth revisiting at least three times: once to learn, once to review, once cold — before the exam — from memory.
The Kata Collection
One concept per kata, drilled until automatic. New to the idea? ↓
🥋 What’s a Kata?
New to the concept? This is the whole idea in 90 seconds.
In karate, a kata (型 — pronounced “KAH-tah”) is a formal sequence of movements practiced repeatedly in the same order until they become automatic. It is performed solo — against an imaginary opponent — drilling each move until the response is reflexive. Mr. Miyagi gave Daniel a kata: wax on, wax off, paint the fence, sand the floor. He never called it training. He just made Daniel do the reps until the blocks arrived before the conscious thought.
In the Dojo, a Java kata is one topic, one page, one complete form to master. Each kata covers everything the AP exam expects you to know cold about one Java concept area: the syntax, the gotchas, the common algorithms, and the exam-day patterns that separate a 3 from a 5. It is not a textbook chapter. It is a form to drill.
Open every section. Read the examples. Understand the gotchas. Run the code. First pass — build the knowledge.
Skip straight to the Quick Reference table at the bottom. Cover the right column. Test yourself row by row. Second pass — find the gaps.
Close the page. Open your IDE. Write the key patterns from memory. Can’t recall a row? Go back. Third pass — the moves are yours.
The AP exam is the sparring match. The kata pages are your practice forms. Mr. Miyagi didn’t apologize for making Daniel wax hundreds of cars — and neither does the Dojo.
Primitive Arrays & the Arrays Class Toolkit
Declaration, String[] args and the motel metaphor, traversal patterns, common algorithms (min/max, sum, reverse, search), the DWR memory-address warning, and the Arrays class as superpower unlock — toString, sort, binarySearch, fill, copyOf.
ArrayList & the Collections Class
The hotel to Kata #1’s motel: dynamic, expandable, method-driven. Import, generics, wrapper classes, core methods (add, get, set, remove, size, contains), the remove-while-iterating trap, and Collections.sort(). Includes a bridge comparison with Kata #1.
The Bridge — Arrays ↔ ArrayList in Action
You have learned the kata separately. Now see them together. ThreeStoogesDriver as the central program: String[] args feeds into ArrayList<String> in a single main. Conversion patterns, side-by-side comparison tables, and the decision guide for choosing which structure to use.
New to S.P.A.R.K.?
The Dojo assumes you’ve heard of the S.P.A.R.K. method. If you haven’t, start with Intro to Prompting — it will change how you use every tool on this page.