Building With People For People: The Unfiltered Build Podcast

The episode has pockets of genuine substance - particularly around inner source conventions, the principal engineer 'altitude' framework, and platform deduplication - but these are heavily diluted by personal career anecdotes, generic AI hot-takes, and platitudinous closing thoughts. The signal-to-noise ratio is low for a 57-minute runtime.

“the software engineer is looking down and at their code... The lead engineer is looking up more, at least laterally to the teams that depend on them... the principal engineer looks another click up and looks out into the industry”

“inner source is just simply using open source inside your company... transferring that open source mindset behind your company's firewall”

The inner source advocacy and the GitHub-topic-tagging convention are underrepresented in most B2B tech podcasts and represent genuine practitioner originality, but the AI section retreads the standard 'it's just a tool/hype cycle' narrative and the career advice is entirely recycled.

“if you add a topic with nike-innersource to your GitHub project, then that is now an Inner Source project”

“I would like to deflate the balloon right off the bat... most of the AI use cases are centered around process automation”

Jeff Bailey is a genuine long-tenure practitioner - principal engineer at Nike running a tech modernization function and a foundation member of Inner Source Commons - giving him real operational credibility, though he is an individual contributor rather than an executive and his industry footprint is limited.

“I've been at the team for now two years. It started out as the Global Platform center of Excellence and we were focused on driving the platform strategy across Nike”

“I'm a foundation member in that community of practice. It is a nonprofit that is global. We have people from Microsoft and IBM”

There are real specifics - named tools, GitHub tagging conventions, CHAOSS metrics, six CMS systems at Nike, 50 - 100 Kubernetes clusters, Amazon Corretto migration - but the episode lacks outcome metrics, cost savings figures, or before/after evidence that would make the claims actionable and verifiable.

“We've got six content management systems. Why?”

“when you have 50 to 100 teams building kubernetes clusters across the enterprise, that's a really expensive proposition”

The host follows the thread reasonably and occasionally lands a decent follow-up (company-size question on inner source, minimum requirements question), but consistently accepts vague answers without pressing for numbers, avoids any productive disagreement, and leans on leading or restatement questions rather than probing ones.

“Do you find that it's kind of a, it's a way, it's sort of a codified, documented way for how teams can structure their projects to enable other teams to know how to use it”

“Amazing. And is there a certain size in which companies are that you would recommend them starting intersource”