Scenario practice for DNS, HTTP, HTTPS, Nginx, release, permission, and certificate failures on a static site VPS.
Difficulty: Applied troubleshooting
What you will test: diagnosis from symptoms, command choice, expected output, and fix checklists.
Work through concrete VPS failure scenarios: DNS answers, HTTP and HTTPS behavior, Nginx status, release paths, file permissions, stale content, and certificate renewal. Each scenario asks for the safest first inspection command before a fix.
Answers/checklists: available as page sections and downloads.
Related project · Related reference page · Related deck
Download lab note · Download cards
Scenario/outcome: Practice verifying a static-site release before and after it goes live on a VPS.
Difficulty: Applied VPS release practice
What you will test: Release folder inspection, current symlink checks, Nginx config validation, DNS, HTTP, HTTPS, www behavior, and rollback notes.
You have a generated static site and a VPS that should serve it from a timestamped release. The lab asks you to prove the files exist, the current symlink points where you think it points, Nginx accepts the config, DNS reaches the expected host, and the live page returns the expected status before you call the release done. A written release note names the active release, the expected public pages, the HTTP and HTTPS status, the DNS answer, the www behavior, and the rollback target. The answer key, checklist, note, and Anki cards are included so the lab can be repeated without an account.
Related project · Related video notes · Related deck
Answers/checklists: answer key on the page, checklist download, Obsidian note, and Anki cards are available.
Download lab note · Download cards · Download checklist
Best next step
Scenario/outcome: Practice checking whether a tiny game loop is complete enough to build on.
Difficulty: Beginner game-loop inspection
What you will test: Player input, game state, win or fail condition, visible feedback, restart behavior, score display, and one controlled improvement idea.
You have a tiny Godot prototype idea. The lab asks you to inspect whether it is a playable loop instead of a pile of disconnected scripts, scenes, assets, and tutorial fragments. One small scene can start, accept player input, change state, show feedback, end or reset, and leave a note naming the next mechanic. The answer key, checklist, note, and Anki cards are included so the lab can be repeated without an account. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related video notes · Related deck
Answers/checklists: answer key on the page, checklist download, Obsidian note, and Anki cards are available.
Download lab note · Download cards · Download checklist
Best next step
Scenario/outcome: Practice documenting a first sensor reading without guessing at wires or voltage.
Difficulty: Careful low-voltage electronics practice
What you will test: Sensor purpose, board voltage, sensor voltage, ground, power, signal pin, expected reading, observed reading, test condition, and next safe adjustment.
You have a microcontroller board and one simple sensor. The lab asks you to prove what each wire is supposed to do, what voltage the sensor expects, and what reading you expect before moving jumpers or adding more parts. The note contains a pin table, voltage expectation, measured or observed reading, test condition, and one next safe adjustment. The answer key, checklist, note, and Anki cards are included so the lab can be repeated without an account. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related video notes · Related deck
Answers/checklists: answer key on the page, checklist download, Obsidian note, and Anki cards are available.
Download lab note · Download cards · Download checklist
Best next step
Scenario/outcome: Practice reading a hydraulic schematic as a diagram, not as a repair permission slip.
Difficulty: Safety-sensitive diagram-reading practice
What you will test: Power source, pump, reservoir, return path, valve, actuator, normal flow path, actuated flow path, unknown symbols, and questions before action.
You have a hydraulic schematic, trainer diagram, or service-manual excerpt. The lab asks you to trace the intended flow path and write questions before touching any equipment. The note marks source, return, actuator, valve state, normal path, actuated path, unknown symbols, safety boundary, and questions for a qualified person. The answer key, checklist, note, and Anki cards are included so the lab can be repeated without an account. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related video notes · Related deck
Answers/checklists: answer key on the page, checklist download, Obsidian note, and Anki cards are available.
Download lab note · Download cards · Download checklist
Best next step
Scenario/outcome: Practice building a local project notebook that turns tutorials, decisions, and cards into a reusable maker record.
Difficulty: Project organization and retention practice
What you will test: Project brief, build log, research notes, troubleshooting notes, decision log, checklists, flashcard capture, and review routine.
You have a real project and too many loose tutorial links. The lab asks you to create a small notebook structure that captures the build goal, decisions, notes, video timestamps, cards, and next actions without becoming a dump. A project notebook exists with a brief, build log, research notes, troubleshooting note, decisions note, checklists note, flashcards note, and a weekly review routine. The answer key, checklist, note, and Anki cards are included so the lab can be repeated without an account. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related video notes · Related deck
Answers/checklists: answer key on the page, checklist download, Obsidian note, and Anki cards are available.
Download lab note · Download cards · Download checklist
Best next step
Scenario/outcome: Create a small folder with two text files. Use pwd, ls -lah, head, and grep to answer where the files are and what each contains.
Difficulty: Applied troubleshooting
What you will test: pwd, ls, and cat tell you where you are and what file you are reading before you change anything.
Create a small folder with two text files. Use pwd, ls -lah, head, and grep to answer where the files are and what each contains. Open a terminal, find files, read output, and run small inspection commands with confidence. Running a command in the wrong directory. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Sketch a release layout with releases/YYYYMMDDTHHMMSSZ and current. Explain how rollback would work.
Difficulty: Applied troubleshooting
What you will test: nginx -t proves configuration syntax before reload.
Sketch a release layout with releases/YYYYMMDDTHHMMSSZ and current. Explain how rollback would work. Understand the path from a local HTML file to a live HTTPS page on a VPS. Reloading before nginx -t. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build. If the next command, measurement, diagram, or sketch feels unclear, pause and write that question before moving on.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Write the sequence you would use to connect a new domain to an existing VPS, including the command that proves each step.
Difficulty: Applied troubleshooting
What you will test: dig +short domain A shows the public A record answer.
Write the sequence you would use to connect a new domain to an existing VPS, including the command that proves each step. Connect a domain to a VPS without guessing whether the problem is DNS, Nginx, or TLS. Changing DNS and TLS at the same time. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Build a test directory where only the parent execute bit is wrong. Use namei -l to identify the break.
Difficulty: Applied troubleshooting
What you will test: namei -l /path/to/file walks every path component.
Build a test directory where only the parent execute bit is wrong. Use namei -l to identify the break. Diagnose why a project file cannot be read, executed, or served. Using chmod -R 777. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build. If the next command, measurement, diagram, or sketch feels unclear, pause and write that question before moving on.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Given a failing service name, list three bounded commands you would run before opening a huge log.
Difficulty: Applied troubleshooting
What you will test: tail -80 logfile reads a bounded slice before deeper searching.
Given a failing service name, list three bounded commands you would run before opening a huge log. Find the relevant log lines for a recent failure without reading the whole log directory. Searching the whole filesystem first. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Change one line in a sample file, inspect it with git diff, stage it, and write a commit message that describes only that change.
Difficulty: Applied troubleshooting
What you will test: git status shows what changed before you commit or deploy.
Change one line in a sample file, inspect it with git diff, stage it, and write a commit message that describes only that change. Make a small project safer to edit, deploy, and roll back. Deploying without checking the diff. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Write a five-command disk-full triage checklist and explain what each command proves.
Difficulty: Applied troubleshooting
What you will test: df -h and df -i separate byte pressure from inode pressure.
Write a five-command disk-full triage checklist and explain what each command proves. Identify whether a disk-full problem is bytes, inodes, journal logs, Docker, or deleted-open files. Deleting random files before proving the owner. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build. If the next command, measurement, diagram, or sketch feels unclear, pause and write that question before moving on.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Describe how you would tell apart a publickey failure from a changed host key warning.
Difficulty: Applied troubleshooting
What you will test: ssh -vvv user@host shows which authentication step fails.
Describe how you would tell apart a publickey failure from a changed host key warning. Debug SSH access without exposing private keys or blindly removing known_hosts entries. Posting private keys. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build. If the next command, measurement, diagram, or sketch feels unclear, pause and write that question before moving on.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a tiny venv, install one package, and prove which python and pip are active.
Difficulty: Applied troubleshooting
What you will test: python -V and which python show which interpreter your shell will use.
Create a tiny venv, install one package, and prove which python and pip are active. Run a project with the intended Python interpreter and dependency set. Installing with one pip and running another python. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build. If the next command, measurement, diagram, or sketch feels unclear, pause and write that question before moving on.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Make a one-room prototype where a test player reaches a goal and resets.
Difficulty: Applied troubleshooting
What you will test: Write the player action in one sentence before adding systems.
Make a one-room prototype where a test player reaches a goal and resets. Create a tiny game loop with input, movement, collision, a goal, and reset. Building menus before the loop. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build. If the next command, measurement, diagram, or sketch feels unclear, pause and write that question before moving on.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Use the widget to choose frames, FPS, tile size, room size, and movement speed. Copy the note, then make one Godot scene that proves those numbers.
Difficulty: Applied troubleshooting
What you will test: Write the verb, sprite states, tile size, and one-room proof before adding art polish or extra mechanics.
Use the widget to choose frames, FPS, tile size, room size, and movement speed. Copy the note, then make one Godot scene that proves those numbers. Create one playable 2D proof with animated player states, tile collision, a goal, and a repeatable export check. Making a large map before one room works. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Use the widget to choose tile size, room dimensions, viewport size, and movement speed. Copy the note, then build one room with floor, wall, gap, goal, and camera limits.
Difficulty: Applied troubleshooting
What you will test: Write tile size, viewport size, room tile count, solid/passable cell rules, and one route before decorating the map.
Use the widget to choose tile size, room dimensions, viewport size, and movement speed. Copy the note, then build one room with floor, wall, gap, goal, and camera limits. Sketch and build a one-room Godot tilemap where the player can see the route, collide with solid cells, reach a goal, and explain the scale. Painting a huge level before one readable room works. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Use the widget to choose incoming velocity, normal angle, and restitution. Copy the note, then reproduce one wall bounce in a tiny Godot scene.
Difficulty: Applied troubleshooting
What you will test: Sketch one contact: incoming arrow, surface normal, reflected arrow, and the value that proves the bounce is repeatable.
Use the widget to choose incoming velocity, normal angle, and restitution. Copy the note, then reproduce one wall bounce in a tiny Godot scene. Build a one-wall Godot bounce proof where incoming velocity, collision normal, outgoing velocity, and energy loss are visible. Changing shape, speed, friction, and restitution at the same time. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Use the widget to choose a parent transform and child local offset. Copy the note, then build one parent marker and child sprite in Godot.
Difficulty: Applied troubleshooting
What you will test: Create one parent marker and one child sprite, then write the child's local offset before changing the parent transform.
Use the widget to choose a parent transform and child local offset. Copy the note, then build one parent marker and child sprite in Godot. Place one child sprite from a local offset, predict its world position, and explain why parent rotation or scale moved it. Moving the child by eye instead of naming the parent and local offset. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Use the widget to choose angle, speed, gravity, and time. Copy the note, then build one projectile scene and compare the preview arc to the actual hit.
Difficulty: Applied troubleshooting
What you will test: Sketch one launch point, one target, one gravity value, and one time window before adding effects or enemies.
Use the widget to choose angle, speed, gravity, and time. Copy the note, then build one projectile scene and compare the preview arc to the actual hit. Build a one-launch Godot proof where the predicted arc, actual projectile path, first hit, and tuning notes can be compared. Tuning speed, gravity, target distance, collision, and animation all at once. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Draw a three-wire sensor connection and mark power, ground, signal, expected voltage, and measurement point.
Difficulty: Careful hands-on practice
What you will test: Disconnect power before changing wiring, then verify voltage before connecting a device.
Draw a three-wire sensor connection and mark power, ground, signal, expected voltage, and measurement point. Inspect a simple controller circuit with less guesswork and fewer fried parts. Moving wires while powered. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build. If the next command, measurement, diagram, or sketch feels unclear, pause and write that question before moving on.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: On a simple cylinder circuit drawing, mark pump, tank, valve, actuator, relief, extend path, and retract path.
Difficulty: Careful hands-on practice
What you will test: Identify the energy source and stored-energy hazards before tracing the circuit.
On a simple cylinder circuit drawing, mark pump, tank, valve, actuator, relief, extend path, and retract path. Explain what a basic hydraulic circuit is trying to do before touching equipment. Treating a schematic like a wiring diagram. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for godot input actions first pass and write what each step proves before moving to the next one.
Difficulty: Applied troubleshooting
What you will test: Create action names before binding keys.
Create a small practice case for godot input actions first pass and write what each step proves before moving to the next one. Make input remapping and controller support easier later. Hard-coding raw key names everywhere. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for godot collision debugging basics and write what each step proves before moving to the next one.
Difficulty: Applied troubleshooting
What you will test: Turn on visible collision shapes before changing physics code.
Create a small practice case for godot collision debugging basics and write what each step proves before moving to the next one. Debug a small collision problem without rewriting the whole player controller. Changing movement code before proving shapes overlap. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for game save system first draft and write what each step proves before moving to the next one.
Difficulty: Applied troubleshooting
What you will test: List the exact state that must survive closing the game.
Create a small practice case for game save system first draft and write what each step proves before moving to the next one. Save and reload one small game state without inventing a full account system. Saving every runtime object. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for multimeter first measurements and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Set the meter mode before touching the probes to the circuit.
Create a small practice case for multimeter first measurements and write what each step proves before moving to the next one. Use a meter to answer a circuit question instead of guessing. Measuring resistance on a powered circuit. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for read a datasheet first pass and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Find the part number and package before trusting a pinout.
Create a small practice case for read a datasheet first pass and write what each step proves before moving to the next one. Find voltage, pinout, absolute maximums, and typical application notes. Using a similar part's pinout. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for motor driver first checks and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Disconnect the motor until logic power and driver wiring are understood.
Create a small practice case for motor driver first checks and write what each step proves before moving to the next one. Bring up a small motor driver safely enough to test direction and speed. Powering a motor from a microcontroller pin. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for stepper motor wiring first checks and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Find the two coil pairs before connecting the driver.
Create a small practice case for stepper motor wiring first checks and write what each step proves before moving to the next one. Wire a small stepper motor without randomly swapping leads. Guessing wire colors. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for cad constraints first sketch and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Define the design intent before adding every dimension.
Create a small practice case for cad constraints first sketch and write what each step proves before moving to the next one. Create a simple sketch that survives later changes. Fully dimensioning random geometry. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build. If the next command, measurement, diagram, or sketch feels unclear, pause and write that question before moving on.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for measure fastener threads and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Clean and inspect the fastener before measuring it.
Create a small practice case for measure fastener threads and write what each step proves before moving to the next one. Avoid mixing similar-looking fasteners that do not actually fit. Forcing metric and imperial threads together. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for welding first safety checklist and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Confirm PPE, ventilation, and nearby combustibles before power-on.
Create a small practice case for welding first safety checklist and write what each step proves before moving to the next one. Prepare a safe practice weld area before learning bead control. Practicing near flammables. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for hydraulic cylinder leak first checks and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Depressurize and make the equipment safe before inspection.
Create a small practice case for hydraulic cylinder leak first checks and write what each step proves before moving to the next one. Describe a cylinder leak clearly before ordering parts or disassembling equipment. Putting hands near pressurized leaks. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for hydraulic pressure vs flow and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Identify whether the complaint is force, speed, heat, or noise.
Create a small practice case for hydraulic pressure vs flow and write what each step proves before moving to the next one. Explain why a slow actuator and a weak actuator are not the same symptom. Calling every hydraulic problem low pressure. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for robot drivetrain first prototype and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Test motors off the ground before adding load.
Create a small practice case for robot drivetrain first prototype and write what each step proves before moving to the next one. Drive a platform forward, backward, and turn reliably. Adding autonomy before manual drive works. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for sensor mounting first pass and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Write what the sensor must see before designing the bracket.
Create a small practice case for sensor mounting first pass and write what each step proves before moving to the next one. Mount a sensor so it can produce useful readings after the robot moves. Printing a final mount before testing position. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for small engine no-start first checks and write what each step proves before moving to the next one.
Difficulty: Careful hands-on practice
What you will test: Make the machine safe and follow the manual before inspection.
Create a small practice case for small engine no-start first checks and write what each step proves before moving to the next one. Describe a no-start problem in evidence terms. Replacing parts randomly. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build. If the next command, measurement, diagram, or sketch feels unclear, pause and write that question before moving on.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for make an obsidian project note and write what each step proves before moving to the next one.
Difficulty: Applied troubleshooting
What you will test: Write the next physical or technical action in one sentence.
Create a small practice case for make an obsidian project note and write what each step proves before moving to the next one. Keep one project note that actually helps you resume work. Collecting links without decisions. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for turn a video into flashcards and write what each step proves before moving to the next one.
Difficulty: Applied troubleshooting
What you will test: Watch for decisions, warnings, and output interpretation, not just vocabulary.
Create a small practice case for turn a video into flashcards and write what each step proves before moving to the next one. Make five review cards that preserve the useful lesson from a video. Making cards for every sentence. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Create a small practice case for read a project error message and write what each step proves before moving to the next one.
Difficulty: Applied troubleshooting
What you will test: Copy the exact first error line and the command that produced it.
Create a small practice case for read a project error message and write what each step proves before moving to the next one. Stop treating every error message as a wall of text. Fixing the last error first. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Draw a packet path for a receive-only Baofeng/APRS learning setup. Label radio, audio interface, decoder, packet fields, license boundary, and the exact point where you stop before transmit.
Difficulty: Applied troubleshooting
What you will test: Start receive-only: identify the radio role, audio path, decoder, expected packet fields, and local rules before touching transmit.
Draw a packet path for a receive-only Baofeng/APRS learning setup. Label radio, audio interface, decoder, packet fields, license boundary, and the exact point where you stop before transmit. Draw a receive-first packet-radio path and explain what a decoded packet proves without assuming transmit permission. Treating a tutorial as permission to transmit. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Enter one frequency into the calculator, copy the estimate note, then write full-wave, half-wave, quarter-wave, velocity factor, and the next verification step before any real build.
Difficulty: Applied troubleshooting
What you will test: Stay receive-first unless you have the right authorization. Write frequency, units, antenna type, and tuning check before any transmit use.
Enter one frequency into the calculator, copy the estimate note, then write full-wave, half-wave, quarter-wave, velocity factor, and the next verification step before any real build. Convert frequency into wavelength fractions, compare meters/feet/inches, apply a velocity factor, and explain why the result is only a starter estimate. Using a frequency without units. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Enter eight angle/RSSI pairs in the widget, copy the Markdown note, then write whether the strongest direction is a clean peak, a broad lobe, or too noisy to trust.
Difficulty: Applied troubleshooting
What you will test: Use only lawful receive-only readings from your own test source or a signal you are allowed to monitor; do not track people or interfere with equipment.
Enter eight angle/RSSI pairs in the widget, copy the Markdown note, then write whether the strongest direction is a clean peak, a broad lobe, or too noisy to trust. Record angle/RSSI pairs, plot a strongest lobe, and explain what the reading suggests without claiming exact source location. Forgetting that -52 dBm is stronger than -80 dBm. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Draw one receive-only ADS-B path. Label aircraft broadcast, 1090 MHz signal, antenna, RTL-SDR, decoder, decoded fields, map display, timestamp, and the limits of your claim.
Difficulty: Applied troubleshooting
What you will test: Stay receive-only. Identify the signal type, 1090 MHz frequency, antenna, receiver, decoder, field list, and lawful-use boundary before installing or sharing anything.
Draw one receive-only ADS-B path. Label aircraft broadcast, 1090 MHz signal, antenna, RTL-SDR, decoder, decoded fields, map display, timestamp, and the limits of your claim. Name the ADS-B frequency, antenna role, receiver role, decoded fields, and map output without confusing receive-only learning with official tracking or transmitting. Confusing ADS-B reception with official radar or air-traffic authority. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Make a 12-stop sweep table at 30-degree increments. Sketch the arm, write two example RSSI runs, mark the strongest lobe, and explain what remains uncertain.
Difficulty: Applied troubleshooting
What you will test: Start receive-only with a lawful test signal and a hand sketch of the rotation before wiring a motor or making a location claim.
Make a 12-stop sweep table at 30-degree increments. Sketch the arm, write two example RSSI runs, mark the strongest lobe, and explain what remains uncertain. Build a repeatable sweep plan: angle steps, antenna orientation, RSSI sample, strongest lobe, repeated run, and uncertainty note. Letting the motor move continuously while logging one unstable RSSI value. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Enter a current point, target point, and speed in the graph widget. Then write the delta vector, length, unit direction, next position, and what extra samples you would need before trusting the motion.
Difficulty: Applied troubleshooting
What you will test: Write the two positions, units, and elapsed time before calculating speed or smoothing the track.
Enter a current point, target point, and speed in the graph widget. Then write the delta vector, length, unit direction, next position, and what extra samples you would need before trusting the motion. Compare two positions, compute the delta vector, divide by elapsed time, and explain speed and direction without hiding units or uncertainty. Mixing pixels, meters, degrees, or grid cells without naming units. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Take ten sample readings from a sensor, RSSI sweep, temperature probe, or simulated list. Write the mean, median, min, max, range, one suspicious reading, and the next repeat test.
Difficulty: Applied troubleshooting
What you will test: Keep the raw readings and units before smoothing, deleting, or explaining away a weird value.
Take ten sample readings from a sensor, RSSI sweep, temperature probe, or simulated list. Write the mean, median, min, max, range, one suspicious reading, and the next repeat test. Read a short sensor log and explain mean, median, range, standard deviation, outliers, and moving-average tradeoffs in project terms. Deleting outliers because they are inconvenient. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Sketch a small game object moving toward a target. Label current position, target position, direction vector, length, and unit direction.
Difficulty: Applied troubleshooting
What you will test: Draw the arrow first: start point, direction, length, and units before writing formulas or code.
Sketch a small game object moving toward a target. Label current position, target position, direction vector, length, and unit direction. Describe a movement, force, sensor direction, or offset as a vector and explain what the numbers mean. Treating a vector as just two random numbers. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Draw a player forward arrow and a target direction arrow. Predict whether the dot product should be positive, near zero, or negative before calculating it.
Difficulty: Applied troubleshooting
What you will test: Normalize direction vectors first when you want an angle-like comparison instead of a size-weighted number.
Draw a player forward arrow and a target direction arrow. Predict whether the dot product should be positive, near zero, or negative before calculating it. Use dot product as a yes/no or how-much signal for facing, projection, lighting, and control problems. Forgetting to normalize when length should not affect the answer. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Draw a rotating pointer, mark radius and angle, then compute where the tip should be for one simple angle.
Difficulty: Applied troubleshooting
What you will test: Write whether the angle is in degrees or radians before using it in code, calculators, or sketches.
Draw a rotating pointer, mark radius and angle, then compute where the tip should be for one simple angle. Move between an angle, a side length, and a coordinate change without guessing. Feeding degrees into a function that expects radians. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Use the widget with one jump or slide example. Change acceleration once, predict the graph, then copy the note and explain whether velocity or position changed first.
Difficulty: Applied troubleshooting
What you will test: Write the axis, units, starting position, velocity, acceleration, and time step before changing a physics value.
Use the widget with one jump or slide example. Change acceleration once, predict the graph, then copy the note and explain whether velocity or position changed first. Connect position, velocity, acceleration, and frame time so a motion change can be predicted before it is tuned. Tuning jump height without writing units or frame time. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Use the widget to create two tones, change sample rate once, copy the note, and explain which peak is useful and what remains uncertain.
Difficulty: Applied troubleshooting
What you will test: Write the sample rate, units, recording length, sensor or source, and expected pattern before reading frequency peaks.
Use the widget to create two tones, change sample rate once, copy the note, and explain which peak is useful and what remains uncertain. Compare a time signal with a frequency view and identify one dominant repeating pattern. Ignoring sample rate and Nyquist before trusting a frequency label. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Use the widget to make two tones and one noise note. Copy the visualizer note, then sketch a Godot, Python, or microcontroller display path with source, sample rate, bars, peak clue, and next repeat test.
Difficulty: Applied troubleshooting
What you will test: Write the audio or sensor source, sample rate, window length, units, display goal, and what the bars should not claim.
Use the widget to make two tones and one noise note. Copy the visualizer note, then sketch a Godot, Python, or microcontroller display path with source, sample rate, bars, peak clue, and next repeat test. Build a first-pass spectrum visualizer plan: source signal, sample rate, FFT bins, bar display, peak clue, and uncertainty note. Building a beautiful visualizer before writing sample rate and window length. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Convert one small project dimension from a sketch into real size, then write the estimate, exact conversion, and a named tolerance.
Difficulty: Applied troubleshooting
What you will test: Write the starting unit and target unit before multiplying anything.
Convert one small project dimension from a sketch into real size, then write the estimate, exact conversion, and a named tolerance. Convert a drawing, measurement, or material estimate into the units the project actually needs. Dropping units halfway through the calculation. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Animate a number from 0 to 100 and write what t=0, t=0.25, t=0.5, and t=1 should produce before testing it.
Difficulty: Applied troubleshooting
What you will test: Name the start, end, and progress value before choosing lerp, easing, or smoothing.
Animate a number from 0 to 100 and write what t=0, t=0.25, t=0.5, and t=1 should produce before testing it. Explain what start value, end value, and progress value produce a smooth transition. Forgetting what t means. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
Scenario/outcome: Draw a rectangular panel with two holes. Mark the reference edge, centerline, hole spacing, clearance, and diagonal check.
Difficulty: Applied troubleshooting
What you will test: Sketch the part and mark fixed edges, clearance zones, and measurement points before measuring diagonals.
Draw a rectangular panel with two holes. Mark the reference edge, centerline, hole spacing, clearance, and diagonal check. Check a physical layout with diagonals, offsets, spacing, and clearance before making a permanent cut. Measuring from a rough edge without naming it. Keep the note tied to a concrete maker project so the lesson does not become a saved link with no next action. After reading, choose one related lesson or practice task and produce a small proof that the idea works in your build.
Related project · Related reference page · Related deck
Answers/checklists: source ladder includes checks, traps, and practice prompts.
