The lights went down in a sixth grade robotics class in Batangas, and a cartoon came on.

I had been in the room maybe ten minutes. The tables were already set with batteries, bulbs, buzzers, and those little spools of wire that unravel the second a child touches them. Everything was staged for a build. This was the first circuit day of the unit, and I had my notebook open expecting to write down something about materials management, because that is the kind of thing I write down.

Instead I watched a Bible story. Two men built two houses, one down low by the river and one up high on the mountain, and then a flood came. The video ended, the lights came up, and Michelle handed out wire.

The flinch

I want to be accurate about my own reaction, which was not admiration. It was a small internal stumble, the kind you feel in your chest before you have language for it. Something in me went *wait*.

I have been teaching in New York City public schools for a decade, and I have absorbed a rule so completely that I stopped experiencing it as a rule. Science class is where we do science. Values live down the hall in advisory, or in the poster above the door, or in the two minutes after someone says something unkind. They do not get fifteen minutes at the front of a lesson on circuits.

I did not say any of that out loud. I wrote three words in my notebook and underlined them, which is what I do instead of talking.

Lasallian, which is the whole point

De La Salle Lipa was founded in 1962 by the De La Salle Brothers of the Philippine District [LINK]. Their founder, St. John Baptist de La Salle, built schools in seventeenth century France specifically for the children of artisans and the poor, which is a nice thing to hold in your head while you watch a room of eleven year olds pick up wire strippers.

The school describes its mission as teaching minds, touching hearts, and transforming lives [LINK].

So the thing I flinched at was not a personal flourish, or an add-on, or a teacher going off script. It is the stated purpose of the institution, printed on the walls, and I had walked past it on my way into the building.

The story was not the story I knew

Here is where it gets interesting, and where I had to go look something up.

The version we watched has two houses. The riverbank man can walk out his door and bathe in the river every morning. The mountain man has to march down and back, so he bathes less often, and the trip costs him something every single day. The man on the riverbank chose convenience; the other chose endurance.

Then the flood comes. The low house is ruined. And the man on the mountain opens his door and takes his neighbor in.

That last part is not in the Bible. The parable of the wise and foolish builders in Matthew 7 is about rock and sand [LINK]. There is no river, no daily bathing, no mountain, and there is certainly no welcome at the end. In Matthew, the house falls with a great crash and the passage stops.

So somebody, somewhere along the chain between the first century and a YouTube channel, added two things. The first is a running cost, which turns the story into a math problem about paying a little every day versus paying everything at once. The second is a rescue, which turns it from a story about being right into a story about being useful to somebody else.

Michelle picked that version. I have thought about that choice more than almost anything else I saw on this trip.

The circuits

Because here is what they built that morning: circuits in series and circuits in parallel.

A series circuit is one loop. Less wire, fewer junctions, and considerably faster to get working, which matters enormously when you are eleven and the class is forty minutes long. It is also the circuit where one break kills everything. Pull one bulb and the whole line goes dark. Add more bulbs and they all get dimmer, because they are sharing.

A parallel circuit takes more wire, more connections, and more opportunities to make a mistake you then have to find. In exchange, every branch gets full voltage, and when one bulb burns out the buzzer keeps going anyway.

And parallel is not free. More branches means more total current drawn, which means the battery dies sooner. Resilience has a running cost, and in a parallel circuit you can measure it in milliamps.

I keep turning that over. The man on the mountain pays for his house every single day with the walk down to the river. The parallel circuit pays for its redundancy every second it is switched on. The story and the physics agree, right down to the fact that the safer choice costs you something continuously rather than nothing at all.

If you want the version your students' parents will feel in their bones, old strings of Christmas lights were wired in series, which is why one dead bulb took out the entire strand and ruined a family evening.

I should say plainly that I do not know whether Michelle planned any of this. I have not asked her yet, and when I do I will report back. It is entirely possible she chose the video because it is four minutes long and the projector was already on. But I have not been able to stop thinking about it, and I would rather tell you about the possibility than pretend I confirmed it.

Now go help somebody

She had assigned six circuits. When a pair finished all six, her instruction was to go help another group.

What I saw next is the part I most want other teachers to hear, because it is not a triumph. A couple of kids genuinely went over and helped. A few others quietly switched to video games or pulled out homework for another class.

If you have taught anything ever, you know this outcome. I have given that exact instruction dozens of times and gotten that exact split, sometimes with worse ratios. "Go help another group" is an invitation with no role attached, no request from the other side, no end time, and no evidence that anything happened. Given those terms, a phone wins on points.

But watch what she did that I have never done. She spent fifteen minutes at the top of the lesson establishing that the man on the high ground opens his door. She pre-loaded the answer before the problem arrived. It half worked, which is more than my version of it does, because my version does not exist.

Three different kinds of failure

My students build paper rockets. They launch, the rocket flops, and they go back and change the body length, or the nose shape, or the number and placement of fins, and they launch again. I talk about this constantly. Failure is a step in the engineering process, and I want them to feel that in their hands rather than hear it from me.

That is one kind of failure. There are at least three, and I have been teaching one of them.

Failure as data. The rockets. You try it, it stinks, you change a variable, you try it again. American science education is very good at this and I am proud of how good we are at it.

Failure as a given. The parallel circuit does not try to prevent the bulb from burning out. It assumes the bulb will burn out and keeps the buzzer running anyway. That is designing around failure instead of iterating through it, and I teach it far less often, mostly by accident when a circuit happens to be wired that way.

Failure you do not get to redo. The flood. The house is gone, there is no second prototype, and the thing that saves you is your neighbor.

Almost every design challenge I run lives in the first category, because school failure is reversible by design. That is a feature and I would not give it up. But the Philippines sits near the top of global disaster risk rankings and sees roughly twenty tropical cyclones a year [LINK, and check this figure before you quote me]. In Batangas, the third category is not a thought experiment. A flood story in that room is closer to local knowledge than to metaphor.

Which is why the ending she chose lands the way it does. The word for it there is **bayanihan**, and the picture everyone shows you is a group of neighbors carrying an entire house down a road to a new spot. Nobody in that image is being rewarded for having built well. They are just carrying the house.

What I had not noticed about my own room

So here is the turn, and it took me a few weeks to see it.

There was never a version of that robotics class without values in it. There was never a version of *my* class without values in it either. The only variable is whether the teacher says them out loud.

Mine, written down for the first time in ten years of teaching: evidence beats authority. Revising is better than being right the first time. Struggle is the work and not a sign the work is going badly. You share your data. Everybody gets the redo.

Those are moral commitments. I teach them every single day, with tremendous conviction, and I have never once announced a single one of them. I have never even written them on a piece of paper until this paragraph.

I noticed hers because they were unfamiliar. I did not notice mine because in American science education they are so ambient that they register as the absence of values rather than the presence of a particular set.

This is what the perspective work in the Asia Society and World Savvy frameworks is actually asking for, and I had been reading it as a skill I was supposed to teach students. It turns out it applies to the person holding the notebook. The question I came home with, which is not the question I submitted, is this one: what do Filipino educators teach on purpose that many of us leave to chance?

Fifteen minutes on why you help each other, before anyone touches a wire, is a very good answer.

Tim, in the second row

Last November I was in Minneapolis presenting on the Science of Happiness. I had brought my own cables and thought I'd prepared for everything.

My laptop would not connect to the projector. I tried the cables. I tried the other cables. I called over the A/V guy, who looked at it for about eleven seconds and told me, and I quote, "Sometimes Macs just won't connect!" and then walked away.

I was lost, blushing deeply, with a room full of people waiting to hear about the Science of Happiness. There is no version of that talk without the slides. I was standing there doing the internal math on whether I could describe a bar graph out loud to forty adults.

And a man in the second row called out, "Hey, wanna use my laptop?"

Tim freakin saved the day. He walked his laptop up, I loaded my deck off a drive, and the session ran twelve minutes late and otherwise fine.

I bring this up because I built on the mountain. I brought the cables. I had prepared, in the specific way the parable tells you to prepare, and it happened anyway. There was no second run of that session and no revised prototype. What saved me was a stranger with a working laptop who had no particular reason to offer it.

Preparation is not a floodwall. That is exactly why the room matters.

TL;DR

- Tell a story before you write the charter. I co-create expectations with my students every September, which I still believe in, but a charter is a list and a list gives them nothing to point at. Nobody has ever said "remember bullet three." Students will absolutely say "we're on the riverbank right now." Three minutes of Tim in Minneapolis, then write the charter as an answer to it.

- Make helping a job instead of an invitation. The stuck group requests a consultant, so help is asked for rather than imposed. Questions only, hands off the wires, with three stems on a card: *show me where you think the electricity stops, what have you tried, what's different between yours and the diagram.* Five minutes, then back to your own bench. The consultant writes one sentence about what the group figured out. And offer consultant *or* the extension challenge, so helping never reads as the punishment for finishing early.

- Ask what the design is best at and what it gave up. "What is your circuit best at? What did you trade away to make it that way?" Kids arrive believing there is one right answer and their job is to locate it. There are several, and each one comes with a bill.

- Say your values out loud at least once. You have them. They land better named than absorbed.

No system is perfect, including mine and including theirs, and the goal is to be a little better than we were the day before. I am not suggesting we import a parable into a New York City public school, which I could not do and would not want to. I am suggesting that the fifteen minutes had a job, and that my fifteen minutes are currently doing nothing.

The lab was the same. The circuit was the same. The fifteen minutes before it were not.