Philosophy of Building Software and Introducing Statsig

6min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

The hosts discuss the philosophy of building software, debating whether it should be unique to your team or bought unless requiring a unique capability. They also talk about the challenges of determining uniqueness and dependency management. Later in the chapter, the founder of Statsig shares their company's inception story and how their tools help engineers understand the impact of new features.

Jerod goes one-on-one with our old friend Justin Searls! We talk build vs buy decisions, dependency selection & how Justin has implemented POSSE (Post On Site Syndicate Elsewhere) in response to the stratification of social networks.

Leave us a comment

Changelog++ members save 9 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

Statsig – Build faster with confidence. Startups to Fortune 500s rely on Statsig to make data-driven decisions. Ship smarter and faster with the unified platform for feature flags, experimentation, and analytics. Our listeners get free white-glove onboarding, migration support, and 5 million free events per month.
Neon – The fully managed serverless Postgres with a generous free tier. We separate storage and compute to offer autoscaling, branching, and bottomless storage.
Fastly – Our bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com
Fly.io – The home of Changelog.com — Deploy your apps and databases close to your users. In minutes you can run your Ruby, Go, Node, Deno, Python, or Elixir app (and databases!) all over the world. No ops required. Learn more at fly.io/changelog and check out the speedrun in their docs.