In ten-plus years of building software, I have never once heard anyone praise a system for being slow. “This database is wonderful, look how long it takes” is a sentence that does not exist. In my world we optimize for p99 latency: we obsess over the slowest one percent of requests, the stragglers, the tail. Slow is not a personality trait. Slow is a ticket, a page at 2am, a post-mortem with your name in it. Spend a decade there and it sets in your bones; you become a person who will not, under any circumstances, be the slow one.

And then you have a baby. And every authority you’ve learned to trust starts telling you to slow down.

The Montessori approach says it plainly: after a baby comes, slow everything down. It is what your body is asking for. It is how your child learns, not in a sprint but in long, unhurried, maddening repetition. Slow is the feature. Slow is the point.

So you stand there holding both truths, and you start to wonder: should I slow down? And underneath that, the scarier one. Can I?

Here is what nobody warns you about: long before you get to decide, the slowing has already happened to you, without your signature on it. Your career takes a backseat in the first trimester, when the smell of your own kitchen is a personal attack. It takes a backseat in the third, when you are gasping for air and getting up to pee every ninety minutes and still attending birth classes, breastfeeding classes, wrapping up work for a clean handover. Then you return, to a baby who wakes multiple times a night and must be rocked to sleep, because no one else on earth is authorized to do it.

And here is the part that undoes me: even when you don’t slow down, even when you grit your teeth and keep every commitment, you come back to find the projects shipped without you, the colleagues promoted ahead of you, and AI calmly writing the code you used to write by hand. You didn’t slow down. You just couldn’t keep up. The treadmill raised its speed while you were gone and forgot to tell you.

So I couldn’t help but wonder: if not slowing down already cost me this much, what would slowing down on purpose cost? Would I join some permanent underclass of the once-promising? Would the work simply route around me, the way a system routes around a slow node? Would I ever get to come back at all? And underneath all of it, the question I am almost afraid to type: is a career like this even worth defending, the kind with no slack in it and the layoffs always idling in the background, or is it just something I’ve been taught never to question?

But there is a term from my own world I keep forgetting to apply to my own life: eventual consistency. In distributed systems you give up on the fantasy that every copy of the data is identical at every instant. Too expensive, too brittle, impossible at scale. So you promise something gentler, and something braver: the system will converge. Not now, not synchronously, but it will get there, and getting there late is a guarantee, not a failure. The data isn’t lost. It’s in flight. I have spent ten years terrified of being the slow request, the one that gets flagged and optimized and killed, and it never once occurred to me that I might not be a bug at all. That a body recovering, a child learning in slow loops, a career on a long and deliberate pause might not be defects in a system that worships speed. They might just belong to a different system, running a different promise.

For about a day, that comforted me. Then I remembered the rest of the definition. The whole gentle promise rests on one assumption nobody says out loud, that the partition heals, that the disconnected node rejoins. Eventual is doing an enormous amount of quiet work in that word. It assumes someone is still trying to reach you. And nobody can tell me how long my partition lasts, or whether the system is still routing to me at all, or whether it converged just fine without me, promoted around me, and won’t much notice when I come back online. I want to believe I’m in flight and not dropped. Most nights I can’t tell the difference.

And then he wakes.

He looks at me and smiles and reaches and buries his face in my neck, and none of it is conditional on how I performed today. The industry can replace me in a heartbeat. To him I am the single most important person alive, and he did not have to read a promo packet to decide it. Who could raise him better than me? No one. Would raising him quench the other thirst, the one for hard problems with my name on them? No. Does he deserve the best of me, and do I deserve these hours with him that I keep apologizing to my calendar for? Yes, and yes, and the answers refuse to agree. For a few minutes the outside world goes quiet. I forget the tail, the partition, the colleagues pulling ahead. I just hold the warm weight of him, grateful for his hands, for a kind of happiness that comes with no strings and asks me to optimize nothing. It is the only contentment I have ever known that no promotion could give me and no layoff could take.

It doesn’t fix the fear. The two hungers don’t trade; feeding one has never once fed the other. So I hold both: the boy who is certain of me, and the career I am no longer certain of. And later, in my one quiet, unoptimized hour, still flinching at the word slow, still reading “p99” as a personal accusation, still terrified of opening LinkedIn and watching everyone else converge without me, I run the only query I care about, the one with no index and no answer:

Is anyone still waiting for this node to come back?

It has been three and a half hours since my son last ate, and he has decided that the most pressing matter in his life is not milk but the eight inches of floor between him and the table leg.

I am trying to nurse him. He is doing the worm.

Somewhere in a browser tab is an online course that told me, in a very calm voice for a very specific fee, that a baby this age should feed every three to four hours. That I must leave a forty-five-minute moat between milk and solids, or the solids will storm in and displace the milk; and the milk, apparently, is still the main event. Somewhere in a book is the rule about wake windows: no more than three hours awake at this stage. Over by a minute and he is overtired. Under by a minute and he is undertired. There is, I am assured, a just right. There is always a just right. It is always one degree away from where I am standing.

And under all of it, the chart. My son does not sit high on the weight growth chart. He never has. The pediatrician says he is simply a very active baby. That this is who he is, that he is fine. She says it kindly. And do I believe her? Of course not. Because a mind like mine does not hear he is fine. It hears find a doctor who will hand you a problem to solve. Should I switch pediatricians? The thought arrives fully formed and reasonable-sounding, dressed up as diligence, as though the issue were her judgment and not my need for there to be an issue at all. A refused feed is never just a refused feed. It is a verdict waiting to be written. On him. On me.

And if - if - I get a few ounces into him, I don’t get to rest in the win. Because the next thing is iron. The next meal must be iron-rich, and it must also be a new flavor, a new texture, because the books are very clear: variety now, or a picky eater later. And a picky eater, in my head, is not a picky eater. A picky eater is a referendum on his entire future. We live in a foreign country. I have a career that does not pause. The machines are already doing my job faster than I learned to do it. How are we - how is he - going to afford to be the kind of person who pushes a plate away? No. He will eat the broccoli. He will have his Omega-3s. He will not be chased around a kitchen at age six with a spoon in someone’s hand. He will have the nutrition and the iron and the brain - the big, developed, future-proof brain - because I will optimize it into him one rejected ounce at a time.

There’s a thing we say in engineering. Premature optimization is the root of all evil. You’re not supposed to pour effort into perfecting a system before you even understand what it needs to do. I have, apparently, decided to ignore this for the single most important system I have ever been assigned.

I couldn’t help but wonder: when did love quietly turn into a performance review? When did every feed become a metric, every meal a deposit into a college fund made of neurons, every nap window a deadline I was already late for?

And then my phone rings.

It is my oldest friend; the one from before all of this. Before I was anyone’s mother, when we were just two girls. The most loving Auntie to my baby. She’s in her last trimester. She is calling to tell me that the baby she is carrying has a genetic disorder.

I stop trying. My son, free at last, makes a break for the table leg with the focus of a man who has never once worried about his iron levels.

And I listen to my friend’s voice do the thing a voice does when someone is being very brave on the phone, and my heart breaks in the specific way it only breaks for a person you have known since you were small.

And then, forgive me, the guilt arrives. Because somewhere under the heartbreak is a smaller, uglier voice asking how I dared. How I dared to spend my whole morning at war with a perfectly healthy boy over forty-five minutes and a green vegetable. How I dared to catastrophize a future for a child who is healthy, who is busy, who is hitting every milestone ahead of schedule. Ahead. While my friend sits on the other end of the line recalibrating what “ahead” will even mean.

Here is what I’m learning about a mind like mine. It does not know how to rest. Hand it a healthy baby and it will find the one ounce he didn’t drink. Hand it heartbreak and it will find the gratitude I failed to feel in time. I have a brain that turns everything - milk, iron, love, luck, even grief - into one more thing I could have done better.

I don’t have a tidy ending. I’m not going to tell you I scooped him up and felt nothing but grace. I held him and felt grateful and terrified and guilty and, underneath all of it, still quietly planning the iron. The optimizer doesn’t switch off. Maybe the work isn’t switching it off. Maybe it’s just noticing, every so often, that the system was never broken;

and that I was the only one in the room who actually needed feeding.

Author’s note: Thoughts, guilt, and milk: mine. Sentence polishing: AI assisted. Final say: also mine.

Subscribe now