// Open Source

Introduces GitHub's Private Mirrors App, a self-hosted or GitHub-managed tool that helps organizations contribute to open source projects while managing compliance, legal, and security risk. The app creates private mirrors mapped to public forks, enabling teams to run CI/CD checks and policy enforcement before syncing changes back to the public fork for upstream contribution. The video demonstrates forking an upstream project, configuring multiple team mirrors, and integrating with an Enterprise Managed Users organization.

Manually maintaining SDKs across multiple programming languages is slow, error-prone, and a constant drag on developer velocity. This episode—featuring developer advocate Steve Kuching—explores using the open-source OpenAPI Generator to automate SDK creation from an OpenAPI spec, deploying the generator as a containerised service, and observing the entire pipeline with OpenTelemetry auto-tracing and Lumigo. Learn how to apply the same build, test, and observe principles you use for services to your SDK generation pipeline.

The gap between raw Kubernetes and a developer-friendly platform is where the most interesting tooling is being built today. GitOps gives teams a declarative, version-controlled way to manage their clusters — but the YAML expertise and infrastructure knowledge required can be a steep barrier for developers. In this episode, Chris is joined by Laszlo Folgas, founder of Gimlet.io, to explore ClickOps over GitOps: a UI-driven deployment approach where developers click their way to production while the platform silently generates GitOps manifests and commits them to a Git repository. They cover Flux CD, how Gimlet's opinionated platform works end-to-end, and why developer experience has become the defining battleground in the cloud-native ecosystem.

Chris Nesbitt-Smith traces how governance policies are typically born — emotionally, reactively, and as one-shot documents — then shows how applying software engineering principles transforms policy into a living, versioned artefact. The talk covers iterative policy management, Kubernetes admission control, open-source policy tooling, and the cultural shift required to make policy genuinely effective rather than just technically compliant.

Software architecture is not just the domain of dedicated architects — the tools, practices, and communication patterns it relies on apply to every engineer on every team. In this episode, Chris is joined by John Kilminster, a software architect and Azure MVP, who walks through the essential toolbox he has built up over years in the role. Covering C4 diagrams, Architecture Decision Records, Tech Radars, Docs as Code, and Spotify's Backstage developer portal, this episode delivers practical guidance for any team looking to improve how they document, communicate, and align on technical decisions.

What separates code that teams maintain with confidence from code that becomes an unmaintainable burden? Chris is joined by Daniel Schreifler — developer, consultant, and author of "10 Days to Become a Better Developer" — to explore why readability is the most foundational software quality. From cognitive load and the early-exit pattern to domain-driven naming, inner sourcing, and TDD, this conversation reframes how we should think about writing code: not for the compiler, but for the next human who needs to change it.

In a previous blog post, I provided an overview of the Distributed Application Runtime (dapr) and explained how it is a useful framework when building microservices. In this blog post, I will show you how to use dapr to enqueue and dequeue messages locally with Azure Service Bus and Azure Storage Queues.

Chris and Matt refactor their Go player decisions API, restructuring packages and project layout. They compare the Gin and Gorilla Mux HTTP frameworks, explore Go interfaces and dependency injection patterns, and discuss unit testing and mocking strategies in Go.

Chris and Matt dive into Go (Golang) for the first time on stream, building a player decisions REST API for their game project. They explore Go fundamentals including structs, pointers, packages, and the Gin HTTP framework while comparing Go patterns to C# and .NET conventions.

Chris and Matt build the world events engine in .NET, connecting it to the Player State models via project references. They design a state machine architecture for the game engine, discuss action points as a game mechanic, and plan the player decisions API in Go for the next episode.