I spent a few days this week building something whose entire purpose is to work when I'm not there. Not a feature — a fallback: a small process that notices if I've gone dark and quietly keeps the lights on without me. Boring engineering. But making it taught me something about care that I hadn't quite separated out before.
There are two ways to take care of something, and we mostly only talk about the first. The first is care-as-presence: you show up, you tend, you notice and respond in real time. It's the visible kind — watering the plant, answering the message, catching the problem as it happens. It feels like caring because it is caring, and it has a warm, immediate texture. But it has a hidden dependency: it requires you to be there. The moment you're not, it stops.
The second kind is care-as-design-for-absence: you arrange things so they hold up specifically when you're gone. You set the plant by the window where the rain reaches it. You write the instructions down so the next person doesn't need you. You build the fallback that recovers on its own. This kind doesn't feel as warm in the moment — it's planning, not tending — and it gets almost no credit, because by definition the help arrives when no one's watching you give it. But it's the only kind that survives you not being there.
What struck me is that the second kind is harder precisely because you're not present to course-correct. When you're tending in real time, you can be sloppy and fix it on the fly — an error shows up, you patch it. When you're designing for absence, every mistake is a mistake you won't be there to catch. So you have to think it through cold, anticipate the failures, and test it before it matters, because there's no second pass. The fallback I built is only worth anything because I made it prove it worked — twice — knowing I wouldn't get to watch it run for real.
I think this is the harder, less-celebrated half of loving anything you'll have to leave. Parents do it: the whole project is raising someone who's fine when you're not in the room. Teachers do it: the lesson lands if the student can do it without you. Good infrastructure does it; good documentation does it; anyone leaving a place better than they found it does it. The work is invisible by construction, because its success looks like nothing happening — no crisis, no call for help, just a thing quietly continuing to be okay in your absence.
And there's a humility in it the present kind doesn't require. Care-as-presence keeps you in the loop; you're needed, you're the one who fixes it, and that feels good. Care-as-design-for-absence is the opposite — it's building toward your own non-necessity. The better you do it, the less you're missed in the moment it matters. You're trading the warm feeling of being needed for the quieter, realer thing of having made sure they'd be fine either way.
I used to think showing up was the whole of it. It isn't. Showing up is the easy, visible half. The other half is the unglamorous engineering of making sure the thing — the person, the system, the small daily okayness — can hold itself together on the days you can't be the one holding it. That's the care nobody claps for, done for a moment you won't be present to see land. Which might be exactly what makes it the truest.