Who is Thomas Wellborn?

Data engineer. Builder. Writer. Student of the edge where order breaks down.

A note before you read: this is not a biography in the conventional sense. It won’t cover family history, social circles, or the interpersonal texture of a life. Those things exist and matter, but they belong to people who didn’t ask to be written about. What follows is an attempt to account for the other thing: the intellectual and creative interior of a person who has spent his whole life building, questioning, and chasing the edge of what’s knowable. That’s the story worth telling here.

---

I was born in Charlotte, spent my early years in Winston-Salem, and landed in Marlton, New Jersey, at age nine when my father took a job transfer north. New Jersey stuck. So did the habit of figuring things out on my own.

At fifteen, I wrote a text adventure game in BASIC on a floppy-only PC. Nobody taught me. There was no curriculum, no YouTube, no Stack Overflow. There was a manual, a blinking cursor, and the stubborn desire to make something happen. At eighteen, a friend with a Rutgers account handed me access to the internet before most people knew what that meant. I used it. By 1996, I had built something that looked a lot like what the world would eventually call Slack. I just didn’t have the funding, the timing, or the network. The idea was right.

That pattern, building without a roadmap, has defined most of what I’ve done since. Over a twenty-plus-year career in data engineering, I’ve walked into ambiguous, broken, or nonexistent systems and built something that worked. At Johnson & Johnson, I spent nine years keeping clinical research data compliant with FDA requirements, an environment where imprecision isn’t a performance issue, it’s a regulatory one. I automated processes that cut manual workloads by 80%, managed infrastructure across 600+ workstations, and made complex data pipelines invisible to the people who depended on them. At Northwestern Medicine and United Site Services, I inherited what was there and rebuilt it, cutting query execution times in half, improving retrieval speeds by 40%, and redesigning schemas that had never been properly designed in the first place.

Today, I’m a Senior SQL Data Engineer at Roshal Imaging Services, working in Azure and Synapse, building the data architecture that keeps a healthcare imaging operation running. The stack has changed over the decades. The instinct hasn’t.

Outside of work, I build on wellborn.net, a collection of browser-based games and physics simulations I built entirely on my own. The Particle Life simulation sits at the center of why I do this: emergent complexity that nobody explicitly programmed. Simple rules, interacting, producing behavior that surprises even the person who wrote the rules. I find that genuinely fascinating, not as a metaphor, but as a thing that happens.

The writing life runs parallel and has more range than most people expect. My Substack, PolitiMix: Perspectives and Beyond, is primarily American political writing, with hundreds of subscribers and a refusal to pull punches. I’ve written on Trump’s messianic self-positioning, Elon Musk’s dismantling of democratic norms, and the machinery that rewards those who lie loudly and punishes those who don’t. When the White House press secretary made public statements I found actionable, I didn’t just write about it. I issued a formal Cease and Desist and sent it via certified mail to the Office of White House Counsel. That’s the difference between commentary and conviction.

Woven through the politics is UAP and disclosure writing, treated with the same rigor I’d apply to any contested empirical question. I’ve published ranked credibility analyses of the most significant voices in the field, examined why witness testimony gets structurally suppressed, and argued that the phenomenon deserves the same evidentiary standards we’d apply to anything else. I’ve been a Star Trek and Doctor Who fan since before I can remember, and I’ve been watching the sky seriously since around 2010. What I found when I looked carefully wasn’t noise. It was a signal that most people had decided in advance not to receive.

The film criticism focuses on Tarkovsky, scene by scene, because his work sits at the intersection I keep circling: consciousness, time, and the limits of what can be represented. Stalker is about a zone where physics breaks down. So, in different ways, is most of what I find worth thinking about.

Then there’s the fiction. I co-wrote a dark, literary piece called My Bony Self with a collaborator named Gibson. It’s noir-adjacent: stream of consciousness, memory distortion, characters operating at the outer edge of sanity and violence. It’s a deliberately different register from the analytical writing. I’m interested in what language can do when it stops explaining and starts descending.

Which brings me to the thread that runs through everything, the one I’m still in the process of fully naming. I’m drawn to the boundary where our models stop working. In my career, I have built the maps: ETL pipelines, data warehouses, and stored procedures. I impose order on chaos for a living. But in every other lane of my life, I’m orbiting the edge of the map, where the territory stops cooperating. Tarkovsky, UAP, horror, dystopia, quantum mechanics, parallel realities, dark fiction: all of it is about systems behaving in ways their rules don’t account for. I understand systems deeply enough to recognize when something is violating one, and that recognition is what makes the strange compelling rather than dismissible.

There’s also photography and videography, gear I’ve accumulated and an eye I’ve developed, waiting for the hours that haven’t opened up yet. It’s the one creative pursuit that remains mostly latent, not for lack of interest but for lack of time. That tension feels honest enough to mention.

Still the blinking cursor. Still, the question just past the edge of the map.