The Day the Computer Caught Up to My Brain: When Plain English Became a Programming Language
- Rich Washburn
- 1 day ago
- 7 min read
I was halfway through writing an article about how badly this whole thing had just broken my brain when my phone rang. It was Jimmy. Now, this wasn’t some staged testimonial call. I didn’t send him a survey. I didn’t ask him for a quote. He wasn’t calling to help me finish a thought.
He was calling because he’d been using this thing for about a week in the real world, in the middle of serious work, and he was basically having the exact same holy-shit moment I was. That timing alone was absurd.
I’m sitting there, already humbled out of my skull, trying to put language around a realization that had just landed on me hard. Then reality decides subtlety is overrated and sends me a live witness. And not just any witness. Jimmy Hayes—Founder/CMO at Data Power Supply, where we’re working through some very real, multi-million-dollar projects in the data center and energy space—calls me fired up because he’d just done something that, not very long ago, would have sounded like a lie.
He took information, decks, source material, and instructions, threw them into a Telegram chat, had the system spin up a Base44 app, reviewed it, approved it, published it to LinkedIn, and started getting incredibly high-quality interactions back from it. Not, “it helped me draft an outline.” Not, “it gave me a few ideas.” It made the thing. It published the thing.
The thing went into the world and started pulling real business responses—like connections from Amazon executives—back out of it. And while he’s telling me this, I’m laughing to myself because ten minutes earlier I had been going through my own version of the exact same rupture.
I had asked the bot a very simple question: What exactly are your capabilities here? It answered me. And my first reaction, naturally, was something along the lines of: Yeah, okay, you’re full of shit. Not because I’m cynical for sport, but because we’ve all been living through a time when AI says an awful lot of impressive-sounding things that turn out to be more aspirational than operational. So I tested it. And here’s the part that got me: It wasn’t bluffing. It wasn’t hallucinating its ass off and hoping I wouldn’t notice. It did the thing. That was the moment my internal furniture started moving around.
The Collapse of the Translation Tax
I’ve been building with AI for a while now. I’ve written about it, experimented with it, built apps with it, and spent the last couple of years watching this whole space evolve from "cute trick" to "serious leverage." So this wasn’t my first dance. But this hit different. Because what broke my brain wasn’t just that something got built. I’ve built plenty of things. What broke my brain was the realization that the machine had finally started meeting thought in something close to its native form.
For most of my life, and really for most of the history of software, there has been a translation penalty between human thought and machine execution. You have the idea. Then you translate it into the form the machine requires. Maybe that means C, Python, JavaScript, or whatever flavor of syntactic suffering your chosen domain requires. Maybe it means dragging boxes around in a low-code interface. Even when AI entered the picture, there was still usually a ritual involved. You sat down at the desk. You entered builder mode. You opened the right environment. You got yourself into the posture of implementation. The barrier between “I know what I want” and “I can make this real” was a gate. And for a long time, that gate did more than filter for technical skill.
It filtered for temperament. For access. For the kind of mind that can tolerate long stretches of rigid syntax, invisible errors, and workflows that often feel like arguing with a very literal demon trapped inside a beige filing cabinet. And then today, I’m staring at a system where I can essentially bark intent into a Telegram thread and capability comes back out the other side.
That is not a minor upgrade. That is not a better user interface.
That is the beginning of a world where plain English is starting to function like a real programming language. Read that again, because I don’t think we’ve fully metabolized what that means yet.
Jimmy, without trying to, handed me the cleanest possible receipt for that exact realization. He said, in so many words, what his Achilles’ heel had always been: programming. He never learned to code. But he knew how to think. He knew how to talk. He knew how to solve problems, generate ideas, and move things forward. What he lacked wasn’t intelligence. What he lacked was the old translation layer. The old priesthood. And now that barrier is getting weirdly thin.
When Capability Escapes the Desk
Software is not some niche skill floating around in a sealed technical bubble. Software is how almost everything meaningful in modern society gets expressed. Finance, medicine, education, logistics, media, operations, infrastructure—somewhere underneath it, software is doing the lifting.
If software is the substrate of modern capability, and the interface to creating software shifts from formal code toward natural language, you are watching access to capability explode.
There are millions of people on this planet whose problem was never lack of intelligence, creativity, or vision. Their problem was that the machine only accepted thoughts translated through a very specific syntax.
Now, the machine is starting to accept something much closer to how humans naturally think. This changes the emotional texture of capability. It changes the distance between “I have an idea” and “let’s see if this works.” It means the marketer can prototype. The operator can automate. The founder can test. The salesperson can create tools instead of waiting for them. The person with the idea no longer has to stop at the idea.
For some people—especially those whose minds move quickly, laterally, verbally, recursively, or in ways traditional interfaces have never particularly respected—this feels like liberation. It starts to feel less like using a machine and more like finally having one that can keep up. Because the barrier was never thought. The barrier was translation.
When translation gets cheaper, capability gets closer. When capability gets closer, more people act. When more people act, the entire shape of innovation changes.
The Long Arc of the Interface
There’s a specific kind of awe that only hits when you’ve been swimming in technology currents for a long time. It’s not the hype-cycle rush. It’s quieter. It’s the feeling of recognizing the exact moment the tide changes direction.
When you’ve watched enough eras of tech come and go, you learn that the biggest, world-bending shifts rarely arrive looking polished. They show up looking a little weird. A little clunky. Not fully formed yet. But they have a vector. The pattern is familiar. We’ve seen this arc before. The internet did it. Wireless did it. The cloud did it. Mobile did it. Each time, the shift wasn’t just about the machinery getting faster—it was about the machinery moving closer to the way humans naturally interact with the world.
Command lines did it for a technical few. Graphical interfaces did it for millions. Mobile did it for billions. And this—this strange, exhilarating, slightly absurd era of conversational, generative, intent-driven systems—is the next turn of that wheel. Only this time, the interface that’s changing isn’t the device. It’s the conversation. The difference is that this one feels faster. It’s arriving in a world that is already fully networked, already digitized, and already primed for instantaneous distribution. The substrate is already here. The pipes are laid. So when something like this shows up—something that violently compresses the distance between thought and execution—it doesn’t have to wait for infrastructure to catch up. It lands and immediately starts running downhill.
What Humanity Does Next
After the shock wears off, what’s left is something bigger than adrenaline.
What happens when enough people really get their hands on this? Not just play with it. Not just prompt it for novelty. Not just use it to shave ten minutes off a task. I mean really absorb it and start building natively with it.
Early in every shift, we use the new thing to imitate the old thing. We make the familiar object faster, cleaner, more automated. That’s normal.
But eventually, the deeper creative wave arrives. That’s when people stop asking, “How do I use this to do what I already do?” and start asking, “What becomes possible now that this bottleneck is gone?” That’s the moment I’m excited about.
I have no idea what enough creatives, builders, operators, educators, artists, marketers, and wonderfully unhinged problem-solvers are going to do when this reaches critical mass in their hands. I don’t know what the native forms of this era look like yet. And that uncertainty doesn’t scare me nearly as much as it energizes me. Because some of the most important moments in technology are the ones where you can feel a new capability arriving before you can fully predict its culture.
Yes, there will be chaos. Humanity has never been handed a new level of power and responded with universal elegance. We are going to misuse this, overhype this, and occasionally do something absolutely brilliant with it.
But even with all of that on the table, I still can’t shake the optimism. Because what I saw in this moment—and what Jimmy echoed back to me so perfectly in the middle of it—was not just automation. It was access. It was expression. It was the first real taste of a world where a lot more human capability can make it across the gap into reality.
I’m inspired, humbled, grateful, a little rattled, and deeply curious about what comes next. Because I’ve seen enough to know these moments matter. They point toward a world where the barriers between imagination and implementation keep getting thinner, and where the machine increasingly meets us not on its terms, but on something much closer to ours.
Before I wrap this up, I want to say thank you to Jimmy for what may be the most perfectly timed testimonial I’ve ever received—right in the middle of me trying to write through my own brain-break moment. It was real, unplanned, hilariously on-brand, and exactly the kind of receipt that makes you stop and appreciate when reality decides to annotate your work in real time. And a sincere nod as well to the team at Data Power Supply. We’re doing serious work in serious environments, and there’s something deeply satisfying about seeing these shifts show up not as toys, but inside the world of real infrastructure, real execution, and real stakes.
So here we are.
Still early. Still weird. Still only seeing the first sliver of what this becomes. But I’ve been around long enough to know that sometimes a sliver is all you need. Enough to feel the direction. Enough to recognize the threshold. Enough to know that history just cleared its throat. And enough to make me genuinely excited to see what humanity does next.
Comments