Why did the robot cross the road?

I stumbled across a video of a delivery robot stuck at a crosswalk. It wasn’t broken or confused. It was waiting for a human to press the WALK button.

It had already navigated sidewalks, avoided people, delivered a package like a polite little mule with Wi-Fi. But when it got to the road, it stopped and asked a human to press the button.

And the human got annoyed. Understandable. But was this the robot's fault? It didn’t fail, it just hit the edge of a system that was never built with it in mind. The short story: We keep building these eerily capable systems and then act surprised when they trip over something dumb we forgot to redesign.

So we keep getting frustrated because AI, or platforms, or whatever tool didn’t magically fix our workflow this week. “It doesn’t work.” “It feels off.” “It’s too robotic.”

Maybe.

Or maybe it’s our assumption that if you just add enough tools -- AI for writing, automation for outreach, analytics for everything -- you’ll eventually hit some kind of frictionless flow. But what you usually get is a faster version of a clunky system. We’re forcing new capabilities into old systems and acting surprised when it feels like wearing dress shoes to run a marathon

Consider this: If AI were actually native to how most people work, a lot of those workflows wouldn’t exist in their current form. Steps would disappear. Roles would shift. Some things we treat as essential would look unnecessary.

The robot getting stuck at the crosswalk isn’t the problem. It’s just pointing at one: We keep waiting for smarter technology, when what we actually need are systems that make sense for it.

_________________________

NOTE: The person's actual reaction/response to the robot will be the subject of another post.

Show, Don’t Tell

There’s a moment in every piece of marketing where the audience decides whether they believe you. And in that moment, nothing, and I mean nothing, beats demonstration.

Not flowery claims. Not “premium quality” fluff. Not enough adjectives to smother a thesaurus.

Demonstration is the creative equivalent of flipping on the lights and saying: “Watch this.”

The Heinz Lesson

Two bottles. Heinz vs. Generic. Two identical dollops on a plate. Fast-forward 3 minutes, 39 seconds.

The generic catsup sweats like it’s in a job interview. Heinz stays thick, proud, and fully composed.

The line: “Actual photograph of water running out of other catsup… One reason you may pay a little more for Heinz.”

No bragging. No begging. Just proof.

That’s demonstration: the kind of truth people can’t unsee.

Other Masters of the Reveal

Blendtec’s “Will It Blend?”

A guy in a lab coat obliterates iPhones, golf balls, and garden rakes. No features list needed, the blender turns absurdity into credibility.

Dyson vacuums

James Dyson didn’t say “better suction.” He dumped piles of debris on floors and showed every competitor leaving a mess. Demonstration in the universal language of dirt.

Apple product launches

Steve Jobs didn’t claim the iPod was small. He pulled it from his jeans pocket and nailed it with the line: “1,000 songs in your pocket." Boom. Demo. Story over.

Swiffer

Their infomercial-style wipe-on/wipe-off comparison made old mops look like medieval torture devices. One swipe = demonstration. Millions of sales.

 

Why Demonstration Works (and Why Writers Forget It)

Writers like telling. Telling is comfortable. But comfortable is not persuasive.

Demonstration forces the audience to participate in the discovery. They see it. They believe it. And belief they arrive at themselves is belief that sticks.

So instead of reaching for the adjective shelf, ask:

What can I show instead of say?

What moment proves the message?

What truth is compelling enough to leave unadorned?

Because the brands that win aren’t the loudest, they’re the clearest. They let the product do the talking, while the copy sets the stage for the sale of either the brand and/or the actual product.

Sometimes all you need is a plate, a dollop, and a little pool of water to say everything.

Music On or Music Off?

 

When people talk about productivity, someone eventually asks: "Do you listen to music while you work?"

The question tends to split the room into two tribes. The music people and the silence people.

The music people talk about it the way athletes talk about pre-game rituals. The perfect playlist. that supposedly turns your brain into a productivity engine.

I’ve tried it. I really have. But most of the time I prefer silence. Not the monastery kind of silence. Just ordinary quiet. The hum of the room. A keyboard clicking away. Maybe the faint sound of a truck going by outside. Just enough stillness for thoughts to stretch their legs without tripping over a drum solo.

Music, for me, tends to behave like a guest who doesn’t understand they’re supposed to be in the background. Especially if there are lyrics. The moment someone starts singing, my brain abandons the sentence I’m writing and runs after the words like a dog chasing a tennis ball. Now I’m halfway through a paragraph and mentally finishing someone else’s chorus.

This is why people who can write while blasting pop music strike me as mildly supernatural. I imagine their brains have some internal bouncer who politely escorts the lyrics away while they continue typing like nothing’s happening.

Mine doesn't have that feature.

Silence, on the other hand, is honest. It doesn’t try to hype you up or set a mood. It just sits there like an empty stage waiting for something to happen.

And when you’re writing, that’s usually what you need: space.

Occasionally, I’ll allow instrumental music … music that knows how to behave. No vocals. No dramatic attempts to steal the spotlight. Just a quiet layer of sound, like fog rolling through the background of a scene.

Even then, however, I keep it low. When I’m writing, music should feel like furniture, not a parade.

Recently, the  “music while working” conversation has been focused on optimization ... the magical combination of lo-fi beats and rain sounds engineered by algorithms that promise “maximum cognitive flow.” As if your brain were a coffee machine and all you needed was the right settings.

It’s a nice idea, but the reality is much less glamorous. A lot of writing involves sitting there, staring at a sentence that refuses to cooperate, and trying to nudge it into shape without making it worse. Silence helps with that. It keeps the room from getting crowded.

Music has its place … on walks, in the car, while cooking dinner. But when I’m trying to think, I’d rather not invite a band into the room. My brain already has enough noise in it.

The Fight Over Data Centers That Could Shape the AI Economy PART 2: CON

Communities around the country are rejecting data center projects.

In 2023, two data center projects were canceled because communities pushed back. In 2024, it was six. Last year it jumped to twenty-five. And right now, nearly a hundred projects are facing organized opposition.

Some people see those numbers and worry. I don't.

In fact, it may be one of the healthiest signs of local democracy we've seen in years.

Because for a long time, the assumption was that if a developer showed up with enough money and enough lawyers, communities were expected to say yes. The project was inevitable. The growth was inevitable. The future was inevitable. The public hearing was mostly theater.

But lately people have started asking a surprisingly reasonable question:

"What exactly are we getting in return?"

And that's where the conversation gets uncomfortable.

Because nobody wakes up hoping a giant warehouse full of blinking machines gets built behind the community center. Data centers aren't exactly charming. No windows. No personality. Just a huge concrete box sitting next to a substation.

The difference is that unlike a factory, they employ relatively few people once construction is complete.

Unlike housing, they don't solve a shortage. Unlike a shopping district, they don't create a place where people actually gather.

They consume land, power, water, and infrastructure while often delivering benefits that feel strangely abstract to the people living next door, but enrich tech companies and billionaires.

Cloud capacity. AI training. Reliability. Fast data transfer. Those things matter. But they don't always matter to the specific community being asked to host them. And that's the tension.

Supporters often argue that if a town rejects a project, the investment will simply move somewhere else. That's true. But that doesn't automatically mean the town made a mistake.

We've seen this movie before too.

For most of the twentieth century, communities were told they needed to accept whatever large infrastructure project arrived at their doorstep because progress demanded it. Highways. Industrial facilities. Power plants. Urban renewal projects. The logic was always similar: accept the disruption today because prosperity will arrive tomorrow. 

Sometimes it did. Sometimes it didn't. Sometimes the prosperity flowed elsewhere while the local community kept the noise, traffic, pollution, and land-use consequences. 

History is full of places that were told they were standing in the way of progress when they were actually asking entirely reasonable questions about costs.

Infrastructure has a quiet, ruthless logic to it. But so does self-preservation.

A community's job is not to maximize national computing capacity. A community's job is to look after the people who already live there. Those are not always the same thing.

Right now the new railroad analogy gets thrown around a lot. Data centers are supposedly the railroads of the AI era. Maybe. But railroads connected towns. They moved people, goods, and opportunity directly into local economies.

A data center is different. Most residents will never enter one. Many won't work in one. Some may barely notice what it does at all beyond the transmission lines and substations that accompany it.

That's not an argument that data centers have no value. Clearly they do.

The internet runs on physical infrastructure. AI runs on physical infrastructure. Modern life runs on physical infrastructure. The question isn't whether data centers are useful. The question is whether every community has an obligation to host them.

And the answer may be no.

Sometimes the right decision is to negotiate. Sometimes it's to demand stronger protections. Sometimes it's to ask for a better deal. And sometimes it's to look at a proposal and conclude that the costs outweigh the benefits.

Not every patch of land needs to become part of the next technology boom. Not every community needs to sacrifice its priorities because a developer says the future depends on it.

The train may indeed be coming. But communities aren't required to build a station every time someone lays track in their direction.

History suggests that saying no is sometimes just as important as saying yes.

_________________________

The Fight Over Data Centers That Could Shape the AI Economy PART 1: PRO

The Fight Over Data Centers That Could Shape the AI Economy INTRODUCTION

_______________________

Get the Details: 

• Data center impact on local communities: Balancing growth infrastructure and community outcomes. - Baker Tilly US, LLP/Baker Tilly Advisory Group. LP
  
  
• How data centers are transforming local communities - Fast Company
  
  
• Why are communities pushing back against data centers? - The Harvard Gazette
  
  
• The Debate on Data Center Development: Costs, Benefits, and Community Responses - The Alliance for Civic Engagement 

• From Energy Use to Air Quality, the Many Ways Data Centers Affect US Communities - World Resources Institute