Count the computers in your kitchen. The laptop on the table is one. The others are easy to miss: the microwave's keypad, the oven timer, the fridge thermostat, the kettle that switches itself off. None of them has a screen full of icons, and nobody installs apps on them. Each is a small chip running one program, from the moment it gets power until the day it is thrown away. Learning to build those computers starts with the words, numbers and habits that the rest of this course uses on every page.
The first section names the pieces: what makes a microcontroller different from the processor in a laptop, what firmware is, and how a connected product stacks hardware, firmware, software and the cloud. The second sorts out the names you will meet in shops and forums. "Arduino" can be a company, a set of tools, or one board. "ESP32" can be a family, a chip, a module, or a development board. Other boards, from the Raspberry Pi Pico 2 to the full Raspberry Pi computer, are placed next to this course's two.
The middle two sections are the arithmetic electronics runs on. Prefixes such as milli, micro and kilo turn 0.008 A into 8 mA, and short codes on parts, such as 4k7 and 104, hide a value in three characters. Binary and hexadecimal are how a microcontroller's control registers are described, so the fourth section builds both from scratch, up to reading a register value field by field.
The last two sections are about how to work. One draws the boundary of a safe bench: low-voltage DC only, no mains ever, and the habits that protect you and your chips. The other explains how to use this course: simulating a lab, building it, or both; what "compiled for a board" does and doesn't prove; and the reading routes for readers who arrive with some experience. By the end, a phrase like "a 10 kΩ resistor on an ESP32-S3-DevKitC-1, register value 0x2C" reads as plain information.