Artwork

Content provided by Changelog Media. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Changelog Media or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Debugging

1:10:44
 
Share
 

Manage episode 408979946 series 1024148
Content provided by Changelog Media. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Changelog Media or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

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.

Leave us a comment

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

Sponsors:

  • FireHydrantThe 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.ioThe 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:

Show Notes:

Something missing or broken? PRs welcome!

  continue reading

Chapters

1. It's Go Time! (00:00:00)

2. Meet the guests (00:00:44)

3. Debugging locally (00:02:18)

4. Shared computer debugging (00:12:22)

5. Don't use an else clause (00:18:23)

6. Team size (00:23:30)

7. Sponsor: FireHydrant (00:26:40)

8. Debugging in prod (00:29:18)

9. How long to keep logs (00:33:09)

10. The golden boot (00:37:35)

11. Metrics (00:40:49)

12. Tracing (00:50:05)

13. Unpopular opinions! (00:52:21)

14. Jon's unpop (00:52:40)

15. Bill's unpop (00:53:01)

16. Matt's unpop (01:03:08)

17. Outro (01:09:37)

321 episodes

Artwork

Debugging

Go Time: Golang, Software Engineering

1,259 subscribers

published

iconShare
 
Manage episode 408979946 series 1024148
Content provided by Changelog Media. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Changelog Media or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

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.

Leave us a comment

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

Sponsors:

  • FireHydrantThe 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.ioThe 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:

Show Notes:

Something missing or broken? PRs welcome!

  continue reading

Chapters

1. It's Go Time! (00:00:00)

2. Meet the guests (00:00:44)

3. Debugging locally (00:02:18)

4. Shared computer debugging (00:12:22)

5. Don't use an else clause (00:18:23)

6. Team size (00:23:30)

7. Sponsor: FireHydrant (00:26:40)

8. Debugging in prod (00:29:18)

9. How long to keep logs (00:33:09)

10. The golden boot (00:37:35)

11. Metrics (00:40:49)

12. Tracing (00:50:05)

13. Unpopular opinions! (00:52:21)

14. Jon's unpop (00:52:40)

15. Bill's unpop (00:53:01)

16. Matt's unpop (01:03:08)

17. Outro (01:09:37)

321 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide