Guided course - 5 chapters

Beginner circuits: A Practical Course with Kai Brooks

Kai Brooks teaches Beginner circuits through five practical chapters that move from a clear foundation to guided work, applied decisions, and revision. You will finish with an annotated concept, model, or prototype, a tutor-ready capstone, saved notes, and a repeatable way to continue practicing.

STEM beginners, makers, robotics learners, homeschool projects, and creative tech students 2 hrs 30 min Practice and checkpoints Free curriculum

Start or resume

Your course progress

0 of 5 chapters complete

Next: chapter 1

What you will learn

Build knowledge, use it, and leave with evidence of progress.

Explain the essential Beginner circuits vocabulary through a connected mental model.
Follow and explain a reliable design and engineering workflow in guided practice.
Apply Beginner circuits to a realistic scenario with visible constraints and tradeoffs.
Evaluate and revise an annotated concept, model, or prototype using evidence-based success criteria.
Complete a capstone and leave with a specific next-practice plan.

Before you start

No professional design software is required
Comfort making rough sketches or diagrams is helpful

Useful materials

Paper and pencil or a basic digital drawing tool
A measurement or reference sheet
Optional domain software for learners who already use it

Suggested rhythm

Complete one 30-minute chapter at a time: learn for 10 minutes, practice for 15, then use 5 minutes for the checkpoint and notes.

Course capstone

Beginner circuits concept proposal

Develop a Beginner circuits proposal for a defined user and constraint, then show how critique changed the final direction.

What you will submit

A short design brief
Two alternatives and one developed concept
An annotated final model plus revision note

How it will be reviewed

The proposal answers the brief
Constraints are handled visibly
Annotations explain decisions
Revision responds to evidence or critique

Course chapters

Learn, practice, check, and record what matters.

2 hrs 30 min total

Chapter 1

Beginner circuits: Foundations and vocabulary

Build a dependable mental model for Beginner circuits before trying to memorize isolated details. You will define the essential vocabulary, inspect a worked example, and turn the ideas into a reference you can actually use.

27 min Not complete

Learning objectives

Explain the purpose of Beginner circuits in your own words.
Use the chapter vocabulary accurately in a short example.
Distinguish a strong example from a common misconception.
Create a compact reference for later practice.

Key terms

Start with the purpose

Place Beginner circuits inside a constrained design problem for a specific user, place, or technical need. Name the result a learner is trying to produce and the constraints that make the skill useful.

How Beginner circuits actually works

These are the load-bearing ideas. Everything later in the course is an application of one of them, so it is worth reading slowly and returning to when something stops making sense.

Ohm's law and its three power forms. V = IR relates voltage, current and resistance, and power follows as P = VI, P = I²R, or P = V²/R depending on which two quantities you already know. Picking the form built from your known values avoids an intermediate rounding step.
Series and parallel combine differently. Resistors in series add directly, while in parallel the reciprocals add. A parallel combination is always smaller than its smallest branch, which makes a fast sanity check.
Kirchhoff's laws close the system. The current law states that currents entering a node equal those leaving it, and the voltage law states that voltage changes around any closed loop sum to zero. Together they solve networks that series and parallel reduction cannot simplify.

Misconceptions worth clearing early

Each of these is common, understandable, and expensive to leave in place. Recognising them now saves rework later.

Adding parallel resistors as if in series. Series addition is taught first and quietly becomes the default habit. Fix: Add the reciprocals instead, then confirm the answer is smaller than the smallest branch resistance.
Forgetting to square the current in P = I²R. The formula gets recalled as IR, which is actually voltage. Fix: Track units: amps squared times ohms gives watts, whereas amps times ohms gives volts.
Designing at full size only. The working canvas flatters the design. Fix: Check at the real size and distance, and on a small screen, before deciding anything is finished.

Build the mental model

Connect the key terms as a process rather than a word list. Use this sequence: define the constraint, sketch alternatives, build a testable representation, and revise from critique.

Catch the common miss

Compare a surface-level attempt with one that shows clear requirements, coherent decisions, technical or visual consistency, and useful iteration. Explain the single difference that matters most.

Equation in context

Ohm's law

V=IR

Voltage, current, and resistance form the basic relationship for a resistive component.

Live circuit

Feel how voltage and resistance fight over current

Raise the voltage, then raise the resistance. The current responds to both, instantly.

V = IR is a tug of war: voltage pushes charge around the loop while resistance holds it back, and the current is the settlement they reach.

Double the voltage and read the current. Exactly double?
Now double the resistance instead and compare.
Find two different settings that produce the same current.

Microcontroller code

Set up one visible output

1 2 3 4 5 6 7 8 9 10 11 12

const int statusLed = 13;

void setup() {
  pinMode(statusLed, OUTPUT);
}

void loop() {
  digitalWrite(statusLed, HIGH);
  delay(250);
  digitalWrite(statusLed, LOW);
  delay(750);
}

1 / 8

Make state explicit const int statusLed = 13;

A named value is created or updated so later behavior can refer to it.

Verify component limits and pin assignments, then test one behavior at a time on real hardware.

Side-by-side comparison

Two proposals for the same brief

Both attempts look plausible from a distance. Toggle the highlights and study where they part ways.

Aspect	Style-first concept	Constraint-first concept
Requirements	The brief quietly redefined to fit the idea	The idea shaped to fit user, space, and budget
Decisions	Choices justified by taste	Choices annotated with the constraint they answer
Iteration	Critique treated as a threat	Critique folded into a visible revision

Constraints are not the enemy of good design; they are its raw material.

Practice round

Match the Beginner circuits vocabulary

Tap a term, then the definition it belongs to. Wrong guesses cost nothing but honesty.

Retrieval beats rereading: pulling a definition from memory strengthens it far more than recognizing it on the page.

Clear the board once, shuffle, and beat your attempt count.
Say each definition aloud before tapping — then check yourself.

Practice activity - 12 min

Make a one-page field guide

Create a compact field guide that would help a new learner recognize and begin using Beginner circuits.

Write a one-sentence definition and purpose.
Add the four key terms with a plain-language example.
Include one non-example and explain why it misses.
Finish with a three-step starter checklist.

Deliverable

One annotated page or slide that can be reused in later chapters.

Success looks like

The definition is specific.
Examples match the vocabulary.
The checklist is usable without extra explanation.

Knowledge check

Which response best shows a usable foundation in Beginner circuits?

1 question

AIt defines the idea, shows it in context, and explains why the example fits. BIt copies a list of terms without connecting them. CIt starts the final project before identifying the purpose. DIt chooses an answer without checking the situation.

Chapter notes Not started

2
Chapter 2
Breadboards: Guided demonstration

Follow a complete Breadboards example from setup to result, pausing at the decisions that experts often make silently. Then repeat the process with support and check your work against visible criteria.

29 min Not complete
Learning objectives

Sequence the main steps in a reliable Breadboards workflow.

Explain why each important decision is made.

Complete a supported example without skipping verification.

Use a checklist to identify one correction.
Key terms
1

Watch the whole process

Trace a model from the initial prompt to an annotated concept, model, or prototype. Mark each point where the learner must observe, choose, or verify rather than act automatically.
2

Worked example: A 12 V supply across 100 ohm and 200 ohm in series

Follow each step and predict the next before you read it. Predicting first is what turns a demonstration into practice.

Total series resistance is 100 + 200 = 300 ohms.

Current is identical everywhere in a series loop: 12 / 300 = 0.040 A, or 40 mA.

Voltage divides in proportion to resistance: 0.040 × 100 = 4.0 V and 0.040 × 200 = 8.0 V, which sum back to the 12 V supplied.

Power dissipated in the 200 ohm resistor is I²R = 0.040² × 200 = 0.32 W.

That 0.32 W exceeds the 0.25 W rating of a common quarter-watt resistor, so the arithmetic feeds directly into a component choice.
3

Where this usually goes wrong

Watch for these while you work through the demonstration rather than afterwards.

Adding parallel resistors as if in series. Series addition is taught first and quietly becomes the default habit. Fix: Add the reciprocals instead, then confirm the answer is smaller than the smallest branch resistance.

Forgetting to square the current in P = I²R. The formula gets recalled as IR, which is actually voltage. Fix: Track units: amps squared times ohms gives watts, whereas amps times ohms gives volts.

Designing at full size only. The working canvas flatters the design. Fix: Check at the real size and distance, and on a small screen, before deciding anything is finished.
4

Practice with scaffolding

Repeat the model with one detail changed. Keep the prompts visible and say or write the reason for each choice before continuing.

5

Check before feedback

Use clear requirements, coherent decisions, technical or visual consistency, and useful iteration as the quality test. Make one self-correction before asking the tutor to review the result.
Live circuit
Feel how voltage and resistance fight over current

Raise the voltage, then raise the resistance. The current responds to both, instantly.

V = IR is a tug of war: voltage pushes charge around the loop while resistance holds it back, and the current is the settlement they reach.

Double the voltage and read the current. Exactly double?

Now double the resistance instead and compare.

Find two different settings that produce the same current.
Guided flowchart
A complete Breadboards practice run

flowchart LR N1["Read the task"] N2["Model one step"] N3["Try with support"] N4["Verify the result"] N1 --> N2 N2 --> N3 N3 --> N4

Pause at each arrow and explain the decision before moving to the next step.

Step 1 of 4: Read the task
Microcontroller code
Read a digital input safely

C++ Read-only example

1 2 3 4 5 6 7 8 9 10 11
const int switchPin = 4; void setup() { pinMode(switchPin, INPUT_PULLUP); Serial.begin(9600); } void loop() { bool pressed = digitalRead(switchPin) == LOW; Serial.println(pressed ? "pressed" : "released"); }

1 / 7

Make state explicit const int switchPin = 4;
A named value is created or updated so later behavior can refer to it.

Verify component limits and pin assignments, then test one behavior at a time on real hardware.
Practice round
Rebuild the Breadboards method

The steps of this chapter's method, shuffled. Arrange them so they would actually work.

A method is a sequence, not a bag of tips — if the order surprises you, that is exactly the gap worth closing now.

Order the steps, then explain to yourself why step 2 cannot go last.

Shuffle again and solve it in fewer moves.
Practice activity - 15 min
Complete the guided run

Use the chapter workflow to produce an annotated concept, model, or prototype for a slightly changed Breadboards example.
1. Restate the task and constraints.
2. Follow the model one decision at a time.
3. Record the reason for two key choices.
4. Check the result and revise one issue.
Deliverable
A completed guided example with two decision notes and one correction.
Success looks like

The workflow is complete.

Decisions have reasons.

The final check produces a visible correction.
Knowledge check
During guided Breadboards practice, when is the best time to explain a choice?

1 question

During guided Breadboards practice, when is the best time to explain a choice? AAt the decision point, before seeing whether the final result works. BOnly after the tutor supplies the correct answer. COnly when the result is wrong. DAfter deleting the draft and starting over.

Chapter notes Not started

Sign in to save chapter notes to your account.

Ready to complete this chapter? Submit the guided example with decision notes, one self-correction, and the checkpoint response.
3
Chapter 3
Sensors: Applied scenario

Transfer Sensors into a realistic scenario where the prompt is less tidy and more than one option may be reasonable. You will define the constraints, choose an approach, and defend the tradeoff.

32 min Not complete
Learning objectives

Extract the relevant facts and constraints from a realistic scenario.

Generate at least two plausible approaches to Sensors.

Choose an approach using explicit criteria.

Explain the likely consequence of the choice.
Key terms
1

Read the situation

Translate the scenario into a clear task. Separate facts, assumptions, constraints, and information that is interesting but not relevant to Sensors.
2

Choosing well under real constraints

Applied work is mostly judgement under limits: less time, less information, and more competing goals than a textbook example allows. These are the decision rules that hold up in practice.

The layout feels cluttered: Remove or group before resizing; hierarchy problems rarely respond to smaller type.

A stakeholder disputes a choice: Reframe it around the user task or a measurable standard rather than preference.

You have limited time to improve a design: Fix contrast, hierarchy, and touch targets first; they affect every user immediately.
3

Reading the situation before acting

Before choosing an approach, state three things explicitly: what result the situation actually requires, which constraints are fixed rather than preferences, and what evidence would tell you the approach is working. Skipping this step is the most common reason competent work solves the wrong problem.

Ohm's law and its three power forms. V = IR relates voltage, current and resistance, and power follows as P = VI, P = I²R, or P = V²/R depending on which two quantities you already know. Picking the form built from your known values avoids an intermediate rounding step.
4

Practitioner notes

Small pieces of working knowledge that rarely appear in introductory material.

Specify resistors for at least twice the calculated dissipation. A part run right at its rating drifts in value and runs hot even in normal operation.

When measuring, put the meter in series for current and in parallel for voltage. Connecting an ammeter straight across a supply is the quickest way to blow its fuse.
5

Compare real options

Generate two workable approaches and test both against the purpose. Do not hide the tradeoff; name what each option improves and what it gives up.

6

Make the reasoning visible

Produce an annotated concept, model, or prototype and attach a short decision note. The note should make the result auditable, not merely confident.
Live circuit
What a sensor reading is

Many sensors are just resistances that change with the world. Slide resistance and watch the current your board would read.

V = IR is a tug of war: voltage pushes charge around the loop while resistance holds it back, and the current is the settlement they reach.

Double the voltage and read the current. Exactly double?

Now double the resistance instead and compare.

Find two different settings that produce the same current.
Microcontroller code
Read and classify a sensor value

C++ Read-only example

1 2 3 4 5 6 7 8 9 10 11 12 13
const int sensorPin = A0; void setup() { Serial.begin(9600); } void loop() { int reading = analogRead(sensorPin); if (reading > 600) { Serial.println("High"); } delay(100); }

1 / 8

Make state explicit const int sensorPin = A0;
A named value is created or updated so later behavior can refer to it.

Verify component limits and pin assignments, then test one behavior at a time on real hardware.
Practice round
Match the Sensors vocabulary

Tap a term, then the definition it belongs to. Wrong guesses cost nothing but honesty.

Retrieval beats rereading: pulling a definition from memory strengthens it far more than recognizing it on the page.

Clear the board once, shuffle, and beat your attempt count.

Say each definition aloud before tapping — then check yourself.
Practice activity - 18 min
Solve the scenario

Apply Sensors to a scenario from school, work, home, or community life that includes at least two constraints.
1. Write the task, audience, and constraints.
2. Sketch two possible approaches.
3. Choose using three criteria from the chapter.
4. Produce the result and explain one tradeoff.
Deliverable
A scenario response with an option comparison and a short decision note.
Success looks like

Constraints are visible.

Both options are plausible.

The final choice follows the stated criteria.
Knowledge check
What makes an applied Sensors decision defensible?

1 question

What makes an applied Sensors decision defensible? AThe chosen approach follows stated constraints and criteria, with the tradeoff acknowledged. BIt is the first idea that came to mind. CIt avoids mentioning uncertainty. DIt copies the guided example without adapting it.

Chapter notes Not started

Sign in to save chapter notes to your account.

Ready to complete this chapter? Finish the scenario response, compare two options, and explain the selected tradeoff.

Chapter 4

Microcontroller projects: Review and improve

Learn to diagnose and improve Microcontroller projects work with a focused rubric instead of vague judgment. You will separate symptoms from causes, revise the highest-value issue, and document the before-and-after difference.

30 min Not complete

Learning objectives

Evaluate a draft using explicit Microcontroller projects criteria.
Identify the cause behind the most important weakness.
Choose a revision with high impact and reasonable effort.
Explain how the revision changes the result.

Key terms

Use the rubric, not a feeling

Review the work for clear requirements, coherent decisions, technical or visual consistency, and useful iteration. Record evidence for each judgment so feedback points to something observable.

Diagnostic checklist

Run this before you revise anything. Diagnosing first prevents the common failure of polishing the parts that were already fine.

Check: Adding parallel resistors as if in series — is this present in your work?
Check: Forgetting to square the current in P = I²R — is this present in your work?
Check: Designing at full size only — is this present in your work?
Check: Using colour as the only signal — is this present in your work?

The quality bar

This is what finished work looks like in this field. Use it as the standard for your revision rather than a general sense of improvement.

The most important element is obvious within a few seconds
Contrast and target sizes meet published accessibility thresholds
The design survives the real context: small screens, poor light, hurried users

Diagnose before editing

Name the symptom, then ask what decision or missing step produced it. Choose the cause you can address rather than changing everything at once.

Revise and compare

Make one purposeful revision and compare the two versions. Keep the change only if it improves the intended result without creating a larger problem.

Live circuit

Feel how voltage and resistance fight over current

Raise the voltage, then raise the resistance. The current responds to both, instantly.

V = IR is a tug of war: voltage pushes charge around the loop while resistance holds it back, and the current is the settlement they reach.

Double the voltage and read the current. Exactly double?
Now double the resistance instead and compare.
Find two different settings that produce the same current.

Revision flowchart

Evidence-led improvement loop

flowchart LR
    N1["Inspect evidence"]
    N2["Find the likely cause"]
    N3["Revise one issue"]
    N4["Compare versions"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Revise the cause of the highest-value issue, then compare the new result with the original criteria.

Step 1 of 4: Inspect evidence

Microcontroller code

Schedule work without blocking the loop

1 2 3 4 5 6 7 8 9 10

unsigned long previous = 0;
const unsigned long interval = 500;

void loop() {
  unsigned long now = millis();
  if (now - previous >= interval) {
    previous = now;
    Serial.println("Timed check");
  }
}

1 / 7

Make state explicit unsigned long previous = 0;

A named value is created or updated so later behavior can refer to it.

Verify component limits and pin assignments, then test one behavior at a time on real hardware.

Side-by-side comparison

Two proposals for the same brief

Use this pair as your revision rubric: find which column your current draft sits in, one row at a time.

Aspect	Style-first concept	Constraint-first concept
Requirements	The brief quietly redefined to fit the idea	The idea shaped to fit user, space, and budget
Decisions	Choices justified by taste	Choices annotated with the constraint they answer
Iteration	Critique treated as a threat	Critique folded into a visible revision

Constraints are not the enemy of good design; they are its raw material.

Practice round

Rebuild the Microcontroller projects method

The steps of this chapter's method, shuffled. Arrange them so they would actually work.

A method is a sequence, not a bag of tips — if the order surprises you, that is exactly the gap worth closing now.

Order the steps, then explain to yourself why step 2 cannot go last.
Shuffle again and solve it in fewer moves.

Practice activity - 16 min

Run a focused revision cycle

Review a previous Microcontroller projects artifact or the supplied flawed example, then improve the most consequential issue.

Score the draft against three criteria.
Quote or point to evidence for the weakest score.
Name the likely cause and revise it.
Write a before-and-after comparison.

Deliverable

A marked-up draft, revised version, and four-sentence change note.

Success looks like

Feedback cites evidence.
The revision addresses a cause.
The comparison explains a measurable or observable improvement.

Knowledge check

Which feedback is most useful for improving Microcontroller projects?

1 question

AA specific observation linked to a criterion and a realistic next action. BA general statement that the work is good or bad. CA complete replacement made by someone else. DA list of unrelated preferences.

Chapter notes Not started

5
Chapter 5
Safe prototyping: Capstone integration

Integrate the course methods in a compact Safe prototyping capstone. You will define the brief, plan milestones, produce a complete result, gather tutor feedback, and leave with a repeatable next-practice plan.

37 min Not complete
Learning objectives

Translate the capstone brief into milestones and checks.

Combine the course methods without losing the central purpose.

Present evidence for the quality of the final result.

Choose the next skill to practice from the final review.
Key terms
1

Define a finishable brief

Choose a specific audience, result, and boundary for the Safe prototyping capstone. Reduce scope until the project can be finished and reviewed in one focused cycle.
2

Bringing the parts together

A capstone is judged on coherence, not on the number of techniques it includes. Return to the core ideas and make sure the work demonstrates them rather than decorating them.

Ohm's law and its three power forms. V = IR relates voltage, current and resistance, and power follows as P = VI, P = I²R, or P = V²/R depending on which two quantities you already know. Picking the form built from your known values avoids an intermediate rounding step.

Series and parallel combine differently. Resistors in series add directly, while in parallel the reciprocals add. A parallel combination is always smaller than its smallest branch, which makes a fast sanity check.

Kirchhoff's laws close the system. The current law states that currents entering a node equal those leaving it, and the voltage law states that voltage changes around any closed loop sum to zero. Together they solve networks that series and parallel reduction cannot simplify.
3

Standards that make the work credible

These are the marks of work that would be taken seriously by someone who does this professionally.

The most important element is obvious within a few seconds

Contrast and target sizes meet published accessibility thresholds

The design survives the real context: small screens, poor light, hurried users
4

Practitioner notes

Small pieces of working knowledge that rarely appear in introductory material.

Specify resistors for at least twice the calculated dissipation. A part run right at its rating drifts in value and runs hot even in normal operation.

When measuring, put the meter in series for current and in parallel for voltage. Connecting an ammeter straight across a supply is the quickest way to blow its fuse.
5

Build with checkpoints

Plan foundation, first draft, verification, and revision milestones. At each checkpoint, save evidence instead of relying on memory.

6

Present and continue

Present an annotated concept, model, or prototype with a concise rationale. Use the final rubric to choose one strength to retain and one next practice target.
Live circuit
Feel how voltage and resistance fight over current

Raise the voltage, then raise the resistance. The current responds to both, instantly.

V = IR is a tug of war: voltage pushes charge around the loop while resistance holds it back, and the current is the settlement they reach.

Double the voltage and read the current. Exactly double?

Now double the resistance instead and compare.

Find two different settings that produce the same current.
Visual model
Capstone learning loop

The capstone is a complete cycle: define a finishable brief, build, review evidence, then choose the next practice target.
Practice round
Match the Safe prototyping vocabulary

Tap a term, then the definition it belongs to. Wrong guesses cost nothing but honesty.

Retrieval beats rereading: pulling a definition from memory strengthens it far more than recognizing it on the page.

Clear the board once, shuffle, and beat your attempt count.

Say each definition aloud before tapping — then check yourself.
Practice activity - 22 min
Complete the capstone sprint

Create a complete Safe prototyping artifact for a defined audience and purpose, using the course rubric to review it.
1. Write a brief with scope and success criteria.
2. Create the first complete version.
3. Run a self-check and request focused tutor feedback.
4. Revise, present, and set one next-practice target.
Deliverable
A finished capstone, evidence of one revision, and a next-practice note.
Success looks like

The result answers the brief.

Course methods are visible.

Revision follows feedback or evidence.

The next step is specific and achievable.
Knowledge check
When is the Safe prototyping capstone ready to finish?

1 question

When is the Safe prototyping capstone ready to finish? AIt meets the written brief and criteria, includes a reviewed revision, and has a clear next-practice target. BIt contains every possible feature or idea. CThe learner can no longer think of any improvement. DIt looks exactly like the tutor example.

Chapter notes Not started

Sign in to save chapter notes to your account.

Ready to complete this chapter? Submit the completed capstone, revision evidence, rubric review, and one concrete next-practice target.

Make it personal

Turn the public curriculum into your own learning path.

Ask Kai Brooks to adapt the sequence to your level, available time, and goal. The personalized path can then be saved in your workspace.

0 of 5 chapters complete

Build knowledge, use it, and leave with evidence of progress.

Before you start

Useful materials

Suggested rhythm

Beginner circuits concept proposal

What you will submit

How it will be reviewed

Learn, practice, check, and record what matters.

Beginner circuits: Foundations and vocabulary

Learning objectives

Key terms

Start with the purpose

How Beginner circuits actually works

Misconceptions worth clearing early

Build the mental model

Catch the common miss

Which response best shows a usable foundation in Beginner circuits?

Breadboards: Guided demonstration

Learning objectives

Key terms

Watch the whole process

Worked example: A 12 V supply across 100 ohm and 200 ohm in series

Where this usually goes wrong

Practice with scaffolding

Check before feedback

During guided Breadboards practice, when is the best time to explain a choice?

Sensors: Applied scenario

Learning objectives

Key terms

Read the situation

Choosing well under real constraints

Reading the situation before acting

Practitioner notes

Compare real options

Make the reasoning visible

What makes an applied Sensors decision defensible?

Microcontroller projects: Review and improve

Learning objectives

Key terms

Use the rubric, not a feeling

Diagnostic checklist

The quality bar

Diagnose before editing

Revise and compare

Which feedback is most useful for improving Microcontroller projects?

Safe prototyping: Capstone integration

Learning objectives

Key terms

Define a finishable brief

Bringing the parts together

Standards that make the work credible

Practitioner notes

Build with checkpoints

Present and continue

When is the Safe prototyping capstone ready to finish?

Turn the public curriculum into your own learning path.