My neighbor spent yesterday morning clearing a patch of maquis with a bulldozer. I watched him from the fence for a while, coffee in hand, contributing nothing. Then I walked down to check that the cows had water, because it's August in Corsica and that is the one job on this farm that cannot wait until later.
The rest of the year I do engineering at GoodBarber, a mobile app platform. This month, my production system is a herd of cows and a water trough.
This is not a burnout story. I'm fine, the team is fine, nothing is on fire. This is about something I re-learn every summer at my parents' farm and manage to forget again by October: disconnecting is not the opposite of engineering. It's where my engineering comes from.
For the past few months my work has looked like this: agents that draft, publish and verify things through MCP servers, pipelines that touch production, and one rule I repeat so often my team can probably recite it in their sleep: grep and eyes. When an agent says it did something, you go read the actual output, with your actual eyes, before you believe it. And a human stays in the loop for anything that ships. I like this work. A lot. Which is exactly why closing the laptop for two weeks felt harder than it should have. When you love the loop, you stop noticing you're inside it.
The heat arrives before you finish your coffee. By nine the cicadas are at full volume and they won't stop until dark; after a day you stop hearing them, a wall of sound your brain files under silence.
The maquis smells like it's cooking. Immortelle, myrtle, hot dust. When the bulldozer bites into it the smell turns sharp, crushed green and diesel, and my father comments on the neighbor's technique from three fields away.
The trough is a twenty-minute walk, morning and evening. You put your hand in the water, because looking is not enough: the surface can shine while the float valve sits jammed. The cows watch you do this with monumental indifference.The soft tick of the electric fence. On the way back you kick the same pine cone the whole length of the path, because there is nothing else to do. It takes a few days to understand that nothing else to do is the entire point.
My phone lives in the kitchen. Half the property has no signal anyway. Evenings are long: tomatoes that actually taste of tomato, a card game nobody remembers the full rules of, chairs on the terrace facing the dark. When the cicadas finally stop, the silence has a texture. The silence in my apartment is just a machine that hasn't beeped yet.
From the hill behind the house you can see the whole farm at once: which field burned yellow, where the fence sags, where the water runs and where it doesn't. None of that is visible from inside the barn.
For months my days were a hundred items deep. A flaky deploy. A graph doing something odd. An agent behaving strangely at 2 a.m. Every one of those items legitimate, none of them wrong to look at, and together they formed a wall between me and the only question that actually matters: what shape is the system, and where is it sagging?
Two weeks of distance, and the shape comes back on its own. Without opening a laptop, I can tell you the two things that genuinely worry me for the autumn. In June I couldn't have, and in June I had all the dashboards.
Judgment turns out to be a renewable resource with a single supplier: distance from the thing you're judging.
Every engineer carries one around: the bug that survives every fix. You fix it, it comes back wearing a different stack trace. Mine came on vacation with me, uninvited. They always do.
The answer did not arrive at a desk. It arrived on day six, somewhere between the trough and the gate, wet hands, no phone. I didn't write a line of code. I just finally saw it: the whole mechanism at once, including the part every previous fix had been politely stepping around.
Boredom without notifications is not empty time. It's the only state in which the complete model of a hard problem fits in your head, because nothing is evicting it every ninety seconds. A notification doesn't need to be answered to cost you. It only needs to arrive.
We talk about deep work as if it were a scheduling technique. I'd call it something simpler: it's what your brain does by default when nothing is allowed to interrupt it. The farm doesn't teach you to focus. It just stops preventing you.
On a farm in August, urgent is unambiguous. Cows without water is urgent. The smell of smoke on the wind is urgent. Everything else waits, and waiting costs nothing.
The cows don't send alerts, by the way. You find out how they're doing by showing up, twice a day, whether anything is wrong or not. There is probably a monitoring philosophy hiding in that sentence, but I promised myself I wouldn't write it on vacation.
Before leaving I skimmed the threads marked urgent across my inboxes. Dozens. I already know what I'll find when I get back, because it's the same every year: most of them will have resolved themselves, gone stale, or turned out to be someone else's adrenaline. What remains is the real work, and it was there all along, hidden in plain sight under the pile.
Here's the uncomfortable part: I can't tell the two apart while I'm in the pile. Nobody can. Up close, all urgency produces the same cortisol. Telling signal from noise takes distance, and you cannot acquire distance while you're busy responding. The 90% of noise was never a triage failure. It was the absence of the one tool that makes triage possible.
Here is the thing I actually came to say.
Checking the trough with your hand because the surface can lie to you: that is grep and eyes. Walking the fence line instead of assuming it held: that is verification before belief. The rule I repeat to my team all year was not invented at a whiteboard. It was installed here, a long time ago, by people who never wrote a line of code and would never trust a report about anything they could go and check themselves.
The farm and the job run on the same values. Look with your own eyes. Keep a human in the loop. Know the difference between urgent and loud. I don't disconnect to get away from engineering. I disconnect to visit the place my engineering came from, and I come back with the judgment, the unstuck bug, and a short list of the things that actually matter.
The neighbor finished his patch of maquis yesterday. Where there was scrub there is now clean ground, ready for whatever comes next. Two more weeks and it's my turn.
The first thing I'll do back at work is not open a dashboard. I'll go look at the system with my own eyes.