Modern software development is more complex than ever. Teams work across different operating systems, chip architectures, and cloud environments, each with its own dependency quirks and version mismatches. Ensuring that code runs reproducibly across these environments has become a major challenge that’s made even harder by growing concerns around software supply chain security.

Nix is a powerful open-source package manager that builds software in controlled, declarative environments where dependencies are explicitly defined and reproducible. Its functional approach has made it a gold standard for reproducible builds, but it can also be difficult to learn and adopt.

Flox is a company that builds on top of Nix, with increased supply chain security and abstractions that streamline the developer experience.

Michael Stahnke is the VP of Engineering at Flox and formerly worked at companies including Caterpillar, Puppet, and CircleCI. He joins the podcast with Kevin Ball to talk about Flox, building on top of Nix, how reproducibility underpins software security, the concept of “secure by construction, how deterministic environments are reshaping both human and AI-driven development, and much more.

Full Disclosure: This episode is sponsored by Flox.

Kevin Ball or KBall, is the vice president of engineering at Mento and an independent coach for engineers and engineering leaders. He co-founded and served as CTO for two companies, founded the San Diego JavaScript meetup, and organizes the AI inaction discussion group through Latent Space.

Please click here to see the transcript of this episode.

Sponsorship inquiries: sponsor@softwareengineeringdaily.com

The post Flox, Nix, and Reproducible Software Systems with Michael Stahnke appeared first on Software Engineering Daily.