I want to be careful with this one, because the genre of “engineer optimises parenting” deserves the eye-roll it usually gets. My son is not a system to be debugged. But the environment around him is, and treating that environment with the same rigour I bring to a production service is the single most useful thing my job has given my family.
- 01 The reframe is environmental: design predictable interfaces, not a “fixed” child.
- 02 Transitions are the failure mode. Most meltdowns are unhandled state changes.
- 03 Visual protocols externalise working memory — for him, and for the adults too.
- 04 Measure to understand, never to grade. The metric serves the kid, not the spreadsheet.
Interfaces, not instructions
A predictable interface is a contract: given this input, you reliably get that output. For my son, the world’s default interface is noisy and non-deterministic — and non-determinism is exhausting when your nervous system logs every event at full volume.
So we stabilised the contracts. Mornings run the same sequence, in the same order, with the same visual cues. Not because rigidity is virtuous, but because a predictable interface frees up the enormous cognitive budget that unpredictability was silently consuming.
Transitions are unhandled state changes
In software, the bugs cluster at boundaries: the cache invalidation, the deploy, the timezone change. In our home, the hard moments cluster at transitions — leaving the park, ending screen time, the shift from weekend to school night.
Once I started seeing meltdowns as unhandled state transitions rather than “behaviour”, the response changed. You do not punish a service for crashing on an input you never handled. You add a handler.
STATE: screen_time -> STATE: dinner
T-10m verbal + visual countdown card shown T-5m countdown card flips to "5" T-2m choose: pause here OR finish this level T-0 timer sound (chosen by him, predictable) +0 transition object: the same toy carried to the table
FALLBACK: if dysregulated, do not add language. reduce sensory input, offer the transition object, wait.It is not magic and it does not always hold. But handling the boundary explicitly turned a daily 9/10 into a frequent 3/10, and that delta is a childhood.
Measure to understand, not to grade
I track things — sleep, sensory load, which days were hard and what preceded them. The danger here is obvious and I have fallen into it: the moment a metric becomes a grade, it corrupts. A low-regulation day is data about the environment, not a verdict on the child or the parent.
The systems lens is not about turning a child into an optimisation target. It is about taking the load that neurotypical environments offload onto an autistic nervous system and, wherever possible, carrying it in the design of the day instead. That is engineering I am proud of.