Felix Geisendörfer & Michael Knyszek join Natalie to discuss Go execution traces: why they’re awesome, common use cases, how they’ve gotten better of late & more. Leave us a comment (https://changelog.com/gotime/310/discuss) Changelog++ (https://changelog.com/++) members save 3 minutes on this episode because they made the ads disappear. Join today! Sponsors: • Boot.dev (https://www.boot.dev/) – Learn backend development the smart way. Boot.dev is the most captivating, finger-flying, addictive way to learn to code. • Fly.io (https://fly.io/changelog) – 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 (https://fly.io/changelog) and check out the speedrun in their docs (https://fly.io/docs/speedrun/) . Featuring: • Felix Geisendörfer – Twitter (https://twitter.com/felixge) , GitHub (https://github.com/felixge) , Website (https://felixge.de/) • Michael Knyszek – Mastodon (https://hachyderm.io/@mknyszek) , Twitter (https://twitter.com/mknyswe) , GitHub (https://github.com/mknyszek) , Website (https://michael.express/) • Natalie Pistunovich – Twitter (https://twitter.com/nataliepis) , GitHub (https://github.com/Pisush) Show Notes: • Making Go more efficient (Go Time #260) (https://changelog.com/gotime/260) • More powerful Go execution traces (https://tip.golang.org/blog/execution-traces-2024) Something missing or broken? PRs welcome! (https://github.com/thechangelog/show-notes/blob/master/gotime/go-time-310.md)