The Spark in the Garage

Chapter 1: The Spark in the Garage

The Board That Wasn't Meant to Be Found

The garage door groaned like it was filing a complaint. Maya Chen, fifteen and certain that Saturday held nothing more interesting than a calculus problem set she'd already finished, stepped over the threshold into her grandfather's workshop and immediately regretted not bringing a mask. The air smelled of solder, machine oil, and a faint ghost of pipe tobacco that Grandpa Theo had quit in 2003 but that the particleboard shelves still seemed to be honoring.

"You came." His voice came from somewhere behind a tower of stacked plastic bins. "I thought you'd bail and send your brother."

"Lucas has a tournament," Maya said, which was true. It was also true that she'd come partly because Grandpa had mentioned, in the careful offhand way he used when he wanted something, that there were "a few things" in the garage worth seeing before they decided what to do with it.

He emerged holding a yellowed cardboard box like a museum curator who'd been waiting for precisely this visitor. His hands, broad and precise, set the box on the long wooden workbench that dominated the room. The bench was scarred with a history of small explosions: burn marks, ring stains, a slot where someone had drilled and missed three times in a row. Above it hung pegboard covered in tools, each one outlined in marker so it knew where to go home.

"Open it," Grandpa Theo said.

Maya opened the box. Inside, nested in antistatic foam, was a circuit board about the size of a credit card — but thicker, and greener, and covered in tiny black squares and silver rivers of metal trace. A row of gold-plated holes ran down one edge. A small silver rectangle in one corner was labeled, in faded ink, *STM32F103*.

"What is it?" she asked.

"That," said her grandfather, "is the brain of a weather station I built in 2011. It logged temperature, humidity, and barometric pressure to an SD card every ten seconds for six years, two months, and fourteen days before a squirrel chewed through the cable to the rain gauge. I pulled the board off the post last week. The rest of the system is compost." He paused. "The board still works."

"How do you know?"

"Because I never threw a board away without testing it." He reached past her and produced, from a drawer organized with the quiet ferocity of a man who had once worked on satellites, a small black object shaped like a USB stick. He plugged it into a laptop on a side table. Tiny lights on the board began to blink in irregular patterns, like fish breathing. "There's no firmware on it right now. It's asleep. Wait — actually, there's a bootloader still in there. That's why it's blinking. It's saying hello, but it doesn't know what to say."

Maya stared. She'd built websites, modded Minecraft worlds, and once made a Python script that texted her mom every time the school Wi-Fi went down. But she had never looked at a circuit board and felt that it was *looking back at her*.

"Can I take it home?" she asked, before she'd finished thinking about whether she wanted to.

Grandpa Theo smiled. It was the smile of a man who had set a trap and watched it close on exactly the right creature. "You can take it home. But there's a condition."

"What condition?"

"Can you make it do something useful?"

Maya looked at the board, then at him. "Useful how?"

"That's the question, isn't it." He sat down on the rolling stool he kept by the bench and gestured for her to take the other one. "Most kids your age, when I hand them something like this, they try to make it look impressive. They want it to scroll their name across an LED or play a song. That's fine. But the question I want you to ask — the question that separates a tinkerer from an engineer — is *useful for whom, doing what, under what constraints, until when*."

Maya opened her mouth, then closed it.

"I don't expect an answer today," he said. "In fact, I expect you to ask me about fifty questions before you get close. That's the job. But here's the deal. You take the board. You take the laptop, too — it's old, but it still runs. And you take this." He reached behind him and produced, from a hook by the door where one might expect a coat, a flat brown Moleskine notebook, blank, with a small elastic band. "Every great product starts as a question. Write yours down. When you have a working system — even a small one — bring it back and show me. If it does something useful, the board is yours. If not, we talk about what useful means."

"What if I just want to make it blink?"

Grandpa Theo looked at her for a long moment. "Then you make it blink," he said. "And then you think about whether blinking is useful. And then you make it do something else."

Maya didn't fully understand what she was agreeing to. She took the notebook, the board, and the laptop, and on the drive back to her mom's house, the green board riding shotgun in its antistatic foam like a nervous passenger, she felt the first faint shape of a question forming in her mind — not yet in words, just pressure, like a thumb pushing gently against the inside of a balloon.

That pressure has a name. Engineers call it *specification*. But before you can specify a system, you have to understand what kind of system it is.

What exactly *is* the thing in that box? Why is it different from the laptop I'm typing this chapter on, or the phone in your pocket? Why does it matter, and why should you — a teenager in a world already drowning in apps — care?

Those are the questions this chapter is going to answer. And by the end of it, the green board will not be mysterious anymore. It will be a tool. And you'll have made it blink.

Embedded Systems Are Everywhere — and They Outnumber Us

Every day, before you finish breakfast, you have already used hundreds of embedded systems. You just didn't notice, because the entire point of an embedded system is to disappear into the thing it controls.

Your microwave has at least one. So does your dishwasher, your clothes dryer, your refrigerator (probably two — one for the compressor, one for the display), and your electric toothbrush. Your TV remote has four. Your car has somewhere between seventy and one hundred and fifty, depending on whether it's a 2005 Civic or a 2025 EV; they run everything from the airbag firing sequence to the chime that reminds you to put on your seatbelt. Your smart watch has several. The traffic lights at the corner of your street have at least three each — one per lamp, sometimes more. The elevator you took to school contains at least four. The school's HVAC system has dozens. The smoke detector in your hallway has one. The laptop you might use to do homework has ten or fifteen: one in the keyboard, one in the touchpad, one in the webcam, one in the power supply, one in the battery charger, one for each USB port's power negotiation, and so on.

A *system* is embedded when a computer lives inside a larger device, dedicated to one or a few specific jobs, and you'd never call it a "computer" unless someone pointed it out.

The laptop you're reading this on is not an embedded system. Or rather, it's an embedded system wrapped around a general-purpose computer; the chassis contains several tiny embedded brains, but the main CPU runs a full operating system that you can repurpose at will. A microwave has a computer, but it can never become a dishwasher. That's the difference. Embedded means *committed*. It means the silicon has been told, with brutal finality, what its job is, and every line of code, every transistor, every milliamp of current has been optimized around that job.

Three numbers will help you feel how lopsided this world really is.

1. Around the time you were born, the number of general-purpose computing devices on Earth — PCs, laptops, servers, phones — passed one billion. By the time you finish college, that number will probably double. 2. Around the same time, the number of embedded systems on Earth passed twent