by Russ Kohn

The Garden Timer

There's a garden. I planted it. Or had it planted. Full of native grasses, fire resistant, local. In harmony I hope. I put in the drip drip drip system. Which broke day one. Poor fittings. Water flooding the zone.

Like so many things these days.

I bought a timer. Did some research, but not really enough. Cut corners — this one looks good enough. Amazoned it to my place. Installed it. Used it manually. Went to automate it. Bluetooth didn't work. WiFi didn't work. Pairing didn't work. Seems like just another Monday. Nothing ever just works anymore.

Tried the app help section. Lots of terrible UX and crappy weak instructions. Of course I already unplugged it and replugged it. Of course I tried the 5g, the 2.4g, the this net and the that net. And the reset button. And unplugged it again.

So like a peon I waited in the online queue for a poor bedraggled helpdesk clerk in god knows where dealing with god knows how many screens to navigate the terrible authentication loop the model serial number ceremony and the unbelievably bad chat interface to finally after 20 minutes get to the "unplug the gray ribbon cable and count to 20."

Unplug the gray ribbon cable. Count to 20.

So unplugging isn't enough. There must be a battery or capacitor or something buried in there, holding onto its state even when the power's gone. And nowhere — not in their online resources, not in their help system, not in any FAQ or troubleshooting page — do they bother to put that information where a customer could find it.

And we tolerate this level of "customer service" because we will drink the water when we are thirsty.

I keep thinking about that capacitor. The thing that holds charge after you think you've turned everything off. The hidden state that nobody documents because documenting it would mean admitting the system is more fragile than advertised.

How many other places are we carrying hidden state? How many other systems — not just garden timers, but the ones that run our companies, our careers, our assumptions about what we're worth — are holding onto charge from a world that's already been unplugged?

Walking all this way with tech my skill has been the distillation of need to code. Now code is increasingly ephemeral. My son, with no formal training, builds beautiful React applications. My brother spins up vertical market solutions in a weekend. The tools democratized the visible part of the craft — the part that used to take weeks and looked impressive. Anyone can make something that looks right now.

So where is my value? What is my identity? How will I continue to pay the bills?

These aren't theoretical questions. They're the ones I ask myself on a Tuesday afternoon when the garden timer finally connects and I'm standing in the yard realizing the easy part is automated and wondering what's left.

Many of us are in this place this time. We see the storm clouds, we hear the hoofbeats. We don't trust our leaders — they're selling transformation while cutting headcount. We don't trust the pundits — they're monetizing our anxiety. And in this attention based economy it is very hard to know what to believe.

The helpdesk clerk couldn't tell me about the capacitor because the system wasn't built to surface that knowledge. The company couldn't fix it because the incentives don't reward honesty about fragility. And here I am — same problem, different scale. Forty years of assumptions about what I'm worth, and I'm the one who needs to count to twenty.

So that's what this is. This site, these dispatches — it's me unplugging the gray ribbon cable. Documenting the reboot in real time, because I don't think I'm the only one who needs one.

Hello future. I'm Russ. Let's dance.

How this dispatch was made

Every Shifting Ground dispatch goes through a 5-stage editorial pipeline: Sift (find the threads), Thrash (adversarial review for voice and honesty), Forge (expand into a draft), Rattle (final coherence check), and Lint (publish-readiness). The AI assists with structure and pacing. The voice is human. Learn more about how this site is built.

Below is the raw seed — captured live, unedited — alongside the version the pipeline produced. Same voice, different pacing.

Original Seed

Raw, unedited, captured live. ~350 words.

There's a garden. I planted it. Or had it planted. Full of native grasses, fire resistant, local. In harmony I hope. I put in the drip drip drip system. Which broke day one. Poor fittings. Water flooding the zone. Like so many things these days. I bought a timer. Did some research, but not really enough. Cut corners... this one looks good enough. Amazoned it to my place. Installed it. Used it manually. Went to automate it. Bluetooth didn't work. WiFi didn't work. Pairing didn't work. Seems like just another Monday. Nothing ever just works anymore. Tried the app help section. Lots of terrible UX and crappy weak instructions. Of course I already unplugged it and replugged it. Of course I tried the 5g, the 2.4g, the this net and the that net. And the reset button. And unplugged it again. So like a peon I waited in the online queue for a poor bedraggled helpdesk clerk in god knows where dealing with god knows how many screens to navigate the terrible authentication loop the model serial number ceremony and the unbelievably bad chat interface to finally after 20 minutes get to the "unplug the gray ribbon cable and count to 20"... so unplugging isn't enough... there must be a battery or capacitor or something... and nowhere in their online resources, help system etc do they bother to put that info into their materials. And we tolerate this level of "customer service" because we will drink the water when we are thirsty.

In the age of AI this is borderline criminal and companies who do not embrace fast easy customer service AI systems with MCP integration or equivalent so solutions can be found quickly will fall behind. Had I been at my desktop I would have done a deep dive search and maybe AI could have figured it out... but that shouldn't be necessary.

How many other places are we dropping the ball on the commercial side. And once we solve all that how many of us will still have jobs or will they just be different jobs?

Walking all this way with tech my skill has been the distillation of need to code. Now code is increasingly ephemeral. So where is my value? What is my identity? How will I continue to pay the bills?

Many of us are in this place this time, we see the storm clouds, we hear the hoofbeats... and we don't trust our leaders and we don't trust the pundits and in this attention based economy it is very hard to know what to believe.

All that I know is I can't stay inside and wait. I have to walk out and meet the future head on.

Hello future. I'm Russ. Let's dance.

Pipeline Output

5-stage SEASON: Sift → Thrash → Forge → Rattle → Lint. ~850 words.

There's a garden. I planted it. Or had it planted. Full of native grasses, fire resistant, local. In harmony I hope. I put in the drip drip drip system. Which broke day one. Poor fittings. Water flooding the zone.

Like so many things these days.

I bought a timer. Did some research, but not really enough. Cut corners — this one looks good enough. Amazoned it to my place. Installed it. Used it manually. Went to automate it. Bluetooth didn't work. WiFi didn't work. Pairing didn't work. Seems like just another Monday. Nothing ever just works anymore.

Tried the app help section. Lots of terrible UX and crappy weak instructions. Of course I already unplugged it and replugged it. Of course I tried the 5g, the 2.4g, the this net and the that net. And the reset button. And unplugged it again.

So like a peon I waited in the online queue for a poor bedraggled helpdesk clerk in god knows where dealing with god knows how many screens to navigate the terrible authentication loop the model serial number ceremony and the unbelievably bad chat interface to finally after 20 minutes get to the "unplug the gray ribbon cable and count to 20."

Unplug the gray ribbon cable. Count to 20.

So unplugging isn't enough. There must be a battery or capacitor or something buried in there, holding onto its state even when the power's gone. And nowhere — not in their online resources, not in their help system, not in any FAQ or troubleshooting page — do they bother to put that information where a customer could find it.

And we tolerate this level of "customer service" because we will drink the water when we are thirsty.

I keep thinking about that capacitor. The thing that holds charge after you think you've turned everything off. The hidden state that nobody documents because documenting it would mean admitting the system is more fragile than advertised.

How many other places are we carrying hidden state? How many other systems — not just garden timers, but the ones that run our companies, our careers, our assumptions about what we're worth — are holding onto charge from a world that's already been unplugged?

Walking all this way with tech my skill has been the distillation of need to code. Now code is increasingly ephemeral. My son, with no formal training, builds beautiful React applications. My brother spins up vertical market solutions in a weekend. The tools democratized the visible part of the craft — the part that used to take weeks and looked impressive. Anyone can make something that looks right now.

So where is my value? What is my identity? How will I continue to pay the bills?

These aren't theoretical questions. They're the ones I ask myself on a Tuesday afternoon when the garden timer finally connects and I'm standing in the yard realizing the easy part is automated and wondering what's left.

Many of us are in this place this time. We see the storm clouds, we hear the hoofbeats. We don't trust our leaders — they're selling transformation while cutting headcount. We don't trust the pundits — they're monetizing our anxiety. And in this attention based economy it is very hard to know what to believe.

The helpdesk clerk couldn't tell me about the capacitor because the system wasn't built to surface that knowledge. The company couldn't fix it because the incentives don't reward honesty about fragility. And here we are, forty years into building these systems, discovering that the biggest hidden state of all is the one I'm carrying — the assumptions about my own value that are still holding charge from a world that's already been unplugged.

All that I know is I can't stay inside and wait. I have to walk out and meet the future head on.

Hello future. I'm Russ. Let's dance.