Go Time
Go Time
Debugging
In this episode Matt, Bill & Jon discuss various debugging techniques for use in both production and development. Bill explains why he doesn’t like his developers to use the debugger and how he prefers to only use techniques available in production. Matt expresses a few counterpoints based on his different experiences, and then the group goes over some techniques for debugging in production.
Changelog++ members save 4 minutes on this episode because they made the ads disappear. Join today!
Sponsors:
- FireHydrant – The alerting and on-call tool designed for humans, not systems. Signals puts teams at the center, giving you ultimate control over rules, policies, and schedules. No need to configure your services or do wonky work-arounds. Signals filters out the noise, alerting you only on what matters. Manage coverage requests and on-call notifications effortlessly within Slack. But here’s the game-changer…Signals natively integrates with FireHydrant’s full incident management suite, so as soon as you’re alerted you can seamlessly kickoff and manage your entire incident inside a single platform. Learn more or switch today at firehydrant.com/signals
- 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.
Featuring:
- Matthew Boyle – Twitter, GitHub, Website
- Bill Kennedy – Twitter, GitHub, Website
- Jon Calhoun – Twitter, GitHub, Website
Show Notes:
- Limits in Kubernetes - A blog by Bill
- Prometheus
- crawler-hints
- distributed tracing
- service weaver
- encore
- Petr Levels
- Andrea Medda
- Matt’s debugging course
Something missing or broken? PRs welcome!
