Skip to main content

Find your line

Last week I was listening to Adam Grant's Rethink podcast. The guest was Daryl Davis, a black musician who has spent decades doing something most of us would find unthinkable: sitting down face-to-face with members of the Ku Klux Klan and neo-Nazis, listening to them, and through empathy and curiosity, helping many leave hate groups behind.

What struck me wasn't just his extraordinary work. It was also his advice for the rest of us, the ones who can't imagine doing what he does.

Not everyone belongs on the front line

Daryl Davis and Jeff Schoep, who also joined the podcast, are what he calls "on the front lines"—directly engaging with people in hate groups. But Davis readily acknowledges that this isn't for everyone.

"Some people, they can't do that," he explained. "They cannot bring themselves to sit down with a KKK member or a neo-Nazi. 'I can't sit with those people. I'm afraid of them. Or I'm afraid I might punch them out. They just irritate me or whatever.' Got it. You don't belong on the front line."

And here's the crucial part: that's okay.

Davis offers an alternative that transforms feelings of helplessness into purposeful action. If you can't be on the front line, maybe you can be on the back line. Maybe the sideline. Maybe online. The key is to find the line where you feel most comfortable and participate from there.

Find your line.

For me this feels empowering. We often feel paralyzed by social problems because we think we need to be heroes, putting ourselves in uncomfortable or even dangerous situations to make a difference. But Davis is telling us something different: sustainable change requires people working at different levels, in different ways, according to their capacities and strengths.

All lines matter equally

Perhaps the most powerful part of Davis's message is this: "There's no line that you can be on that is any more important than any other line."

The person making meals for organizers on the back line isn't less important than the person on the front line. The person sharing resources online isn't contributing less than the person attending rallies. We need people researching, writing, donating, educating, supporting, organizing, and yes, sometimes directly engaging.

"We all have to work together, put all these lines together," Davis said, "and that's how we create a great society."

 

His words triggered honest self-reflection. Where can I actually show up consistently? Where do my skills, temperament, and circumstances allow me to contribute meaningfully?

What Davis offers is a vision of change that's both realistic and hopeful. It acknowledges our different capacities while insisting that everyone has a role to play. It replaces guilt and overwhelm with clarity and purpose.

So, the question isn't whether you're brave enough to be Daryl Davis. The question is simpler and more personal: What's your line?


To hear the full conversation between Adam Grant, Daryl Davis, and Jeff Schoep, listen to the Rethink podcast episode "Talking people out of hate."

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...