Why "Theoretically Impossible"?

People ask about the name. They usually smile when they hear it — Theoretically Impossible Solutions — and then they ask where it came from. It's a fair question. It's not exactly a name that blends in.

The honest answer is that it started with a line from a film. I won't get into which one — the movie itself doesn't have much to do with what we do here. But there was a scene that lodged itself in my brain early on and never left.

A researcher walks into a job interview. He's a theoretical scientist, but he needs clinical work — he needs a paycheck. The interviewer asks what he's been working on, and the researcher describes this absurdly painstaking task. Extracting some vanishingly small amount of a compound from a truly ridiculous quantity of raw material. The kind of work that sounds like a punchline.

The interviewer pauses. "That's impossible," he says.

The researcher nods. "I know. I proved it."

I couldn't tell you exactly why that stuck with me. Maybe it was the dry humor. Maybe it was the stubbornness of it — the idea of spending a year proving something couldn't be done, and somehow that being a perfectly valid use of a year. But here's what I've learned since then: those journeys are never wasted. Every time I've chased something that turned out to be impossible, I picked up a skill or stumbled onto an insight that I never would have found any other way. The thing I was looking for wasn't there — but something else was, and it turned out to be exactly what I needed later. I don't believe in accidents. I believe those detours are part of the path, even when you can't see where it's going yet.

Mostly, though, I think what stuck was the quiet acknowledgment that the line between "impossible" and "not yet figured out" is thinner than most people realize.

A Mindset Before It Was a Company

Long before Theoretically Impossible Solutions was an LLC with a website, it was a joke I told myself about my career. I started calling what I did "the Institute for the Theoretically Impossible" — partly because it sounded appropriately grandiose, and partly because it was actually a pretty accurate description of my work.

I've spent a large part of my career in the space between "the documentation says this can't be done" and "but what if it can?" Reverse-engineering undocumented features. Pushing past what everyone agreed were "known limitations." Finding solutions to problems that had been written off as unsolvable. Not because I'm smarter than anyone else, but because I'm stubborn enough to keep going after the reasonable stopping point.

There's a quote from the Seabees — the U.S. Navy's construction battalions — that captures this better than I ever could: "With willing hearts and skillful hands, the difficult we do at once; the impossible takes a bit longer." That's always resonated with me. Not the bravado of it, but the matter-of-factness. The impossible isn't some grand, dramatic thing. It's just the stuff that takes a bit longer.

And then there's the other side of it. There's a moment in Smokey and the Bandit where Snowman tells the Bandit that what they're trying to do has never been done. The Bandit's response? "You gotta quit being so negative, son. Of course we can make it. We ain't never not made it before." If the Seabees quote is the professional philosophy — steady, skilled, methodical — the Bandit is the gut instinct. The refusal to even entertain the possibility that it can't be done. Both of those live in the DNA of this company.

From Joke to Reality

So when the time came to actually start a company — to put a name on what I do and hang a shingle out — I didn't have to brainstorm. The name was already there. It had been there for years. "Theoretically Impossible Solutions" was just the formalized version of something that had been true about my work all along.

The "Solutions" part matters, too. I'm not interested in proving that things are impossible. I'm interested in the opposite: taking the things that seem impossible and finding a way through them. The theoretical impossibility is the starting point, not the conclusion.

Why It Matters Now

We're living through one of the most significant shifts in how software gets built. Agentic AI isn't a buzzword — it's a fundamental change in what's possible and how fast you can get there. I've watched projects that should have taken a month get done in a week. I've built and rebuilt development frameworks in the time it used to take to spec one out. The "impossible" is getting redefined in real time.

That's what this blog is going to be about. Not the hype. Not the theoretical potential. The actual, lived experience of working at this edge — where the tools are new, the patterns are still forming, and the people willing to push through the friction are finding things that nobody else has found yet.

This is part one of the story. In the next post, I'll get into the specifics of my own journey into agentic development — how I went from using AI as a code completion tool to building a full agentic development framework in a matter of weeks. That story has its own twists and turns, and I think it says something important about where all of this is headed.

But for now, that's where the name comes from. It's a reminder that "impossible" is usually just a label people put on things they haven't figured out yet.

We figure them out.

← Back to Blog