Skip to main content

About the show

The real-world conditions behind software that has to work

Connective Tissue is a video podcast about what it actually takes to build, deliver, and operate software in environments where technology is only part of the problem.

The premise

Good technology fails inside complex systems all the time. Connective Tissue is about the gap between a promising idea and an operational capability — and the environmental, technical, and human forces that decide whether software survives contact with the real world.

Defense is the initial lens, but the underlying questions are broad enough to resonate with anyone operating critical software in conditions that are high-consequence, regulated, distributed, disconnected, resource-constrained, or simply hard to sustain.

“What has to be true for software to work when the environment does not cooperate?”

Made for leaders

The show is not a tutorial on configuring Kubernetes or building pipelines. Technical detail supports the conversation, but the destination is the decision. A good episode leaves a leader better equipped to:

Understand why these problems persist
See where organizational and technical decisions intersect
Know what questions to ask their teams
Recognize the tradeoffs vendors and programs often hide
Challenge an assumption with more confidence
Decide what to fund — and what to sustain

What makes it different

There are already many shows interviewing founders about emerging technology. We ask a sharper question: where does industry automate complexity versus merely hide it? Guests explain the environment and the problem, not just the product — and are welcome to describe alternative approaches and competing ideas.

Relationship to BrainGu

BrainGu convenes the conversation and lends credibility and perspective — it doesn’t dominate the editorial agenda. Most episodes are problem-led. BrainGu experience appears where it’s genuinely relevant, and SmoothGlue comes up only when the product materially helps explain the topic.

Part of the problem space?

Operators, engineers, program and acquisition leaders, researchers, and vendors with real implementation experience — we’d like to talk.