Course Map
The Book Spine: From First Spark to Validated Hardware
Pick up a finished circuit board and it lies to you. It looks solid. Inevitable. As if someone simply chose the parts, routed the traces and sent it away.
Real hardware is not like that. It is a chain of bets, measurements and recoveries. This book is about learning how to make those bets deliberately, then prove them with instruments.
This is not a quick tour of electronics. A quick tour teaches you how to blink an LED and leaves you alone when the real board browns out, the I2C bus sticks low, the motor cable drops three volts, or the regulator runs too hot to touch.
The point of this course is different: build the mental model that lets you stay with a board until it becomes trustworthy. The early chapters teach the small laws that fit on a napkin. The later chapters use those laws on the messy problems that actually decide whether hardware ships.
The throughline
We keep returning to two physical machines.
The first is small: a battery-powered ESP32 environmental monitor. It reads a sensor, wakes on a schedule, transmits over Wi-Fi and sleeps most of its life. It is simple enough to hold in your head, but rich enough to force real decisions about current, pull-ups, ADC range, sleep state and battery life.
The second is larger: a robot-hand electronics stack. It has a PCB that must survive first power, buses that must talk, motors that must spin, power rails that must stay quiet, cables that must not waste the battery and tests that must catch failures before a customer does. It is not a new subject. It is the same subject with the training wheels removed.
The three arcs
Think of the course as one book in three movements.
| Arc | Chapters | What changes in your head | |---|---:|---| | Foundations | 0-20 | You stop treating voltage, current, resistance, GPIO, ADCs and buses as vocabulary and start using them as prediction tools. | | Bring-up and measurement | 21-36 | You learn how to approach a board that might be wrong, power it without drama and use instruments to separate truth from noise. | | Power, motion and validation | 37-52 | You size motors and power paths, reason about heat, close the loop on reliability and build the tests that make hardware repeatable. |
The order matters. A voltage divider is not a formula to memorize because a later ADC lesson needs it. It is a compact model of how circuits share voltage, and that same model reappears in probe loading, ground bounce, pull-up sizing, cable drop and power distribution. The course keeps circling back to the same ideas at larger scale.
How to read this book
Read it in order the first time. Not because every page is equally hard, but because electronics punishes missing foundations. If you skip current limiting, MOSFETs look like magic. If you skip ground references, oscilloscopes lie. If you skip energy and heat, power electronics becomes a list of converter names rather than a way to move watts without cooking copper and silicon.
For each chapter, do four things:
- Read the story before the math. The story tells you why the equation exists.
- Drive the demo when one appears. Move the controls until the behavior surprises you.
- Do the checks and practice problems before opening the solution.
- Keep a small notebook of predictions, measurements and wrong guesses.
The last item matters. Hardware skill is largely calibrated intuition. You build it by predicting a number, measuring the real thing and noticing the gap.
The shape of a good electronics chapter
Each strong lesson should feel like a chapter from a serious engineering book, not a reference card. It needs a concrete opening, the intuition before notation, at least one worked calculation, a figure or historical anchor, a driveable demo when the idea can be made interactive, and a closing that points forward.
That bar is hard on purpose. Electrical engineering is hard because the visible object is small and the important thing is often invisible: electric field, current loop, charge storage, heat path, timing margin, noise floor. Good teaching has to make the invisible feel mechanical.
Why this is electrical engineering, not an ESP32 tutorial
The ESP32 is a useful recurring character because it gives the early course a real board, real pins and real constraints. But the subject is broader. Ohm's law is not an ESP32 fact. Pull-up timing is not an ESP32 fact. Power loss, probe capacitance, thermal resistance, sampling, grounding and feedback all outlive the microcontroller.
The book starts with the ESP32 because a concrete board keeps the abstractions honest. It ends in measurement, power electronics, motors and validation because that is where the same abstractions become engineering judgment.
Key takeaways
- This course is a sequenced book, not a bag of lessons.
- The recurring machines are a low-power ESP32 sensor node and a robot-hand electronics stack.
- The central habit is prediction followed by measurement.
- The same simple laws reappear at larger scale: in probes, buses, motors, converters, heat and reliability.
- A finished board is trustworthy only after it has survived bring-up, measurement and validation.
The promise is not that electronics becomes easy. The promise is that it becomes legible. A resistor stops being a colored part and becomes a slope. A wire stops being a line and becomes resistance, inductance and heat. A board stops being a mystery and becomes a system you can interrogate.
That is the book we are writing here: how to look at hardware until it starts answering.