Podcast log - June 2024
published 4.7.2024
A log of podcasts that I've listened to in the past month.
Go Time: Ep. 179: Event-Driven Systems
Daniel Selans and Steve High join Jon Calhoun and Kris Brandow to share their experiences with event-driven systems, shedding light on their complexity, benefits, and implementation strategies.
- The complexity of setting up event-driven systems
- Embracing eventual consistency
- Tools for building event-driven architectures
- Real-world examples and best practices
Go Time: Ep. 133: Reflection and Meta Programming
Mat Ryer, Jon Calhoun, and Jaana Dogan discuss reflection and meta programming in Go, exploring how Go's approach differs from other languages and examining practical applications and best practices.
- The role of reflection in Go and its use cases
- Examples of effective and ineffective use of reflection
- Alternative approaches to reflection
- Understanding struct tags in Go code
Go Time: Ep. 317: Your Ultimate Guide to Mastering Go
In this episode, Angelica Hill interviews Samantha Coyle about her newly published textbook, "Go Programming - From Beginner to Professional," which serves as a comprehensive guide to mastering Go for real-world software development success.
- The motivation and process behind writing the book
- Key takeaways and advanced topics covered
- Ensuring the book's relevance in the evolving tech landscape
- Advice for aspiring authors and female Gophers
TOP Go Time: Ep. 256: gRPC & Protocol Buffers
Akshay Shah joins Jon and Johnny to discuss the history of protocol buffers and gRPC, exploring how protocol and implementation variations can lead to issues like binary bloat.
- The evolution of protocol buffers and gRPC
- Differences between protocol specifications and implementations
- Addressing binary bloat in Go's protocol buffer implementation
- Best practices for using gRPC in Go applications
Go Time: Ep. 269: The Bits of Go We Avoid (and Why)
In this episode, Mat, Jon, and Carl discuss the parts of Go they tend to avoid, sharing their experiences and the reasons behind their choices.
- Avoiding certain Go features due to past challenges
- Overused aspects of Go that often lead to refactoring
- Preferred alternatives to less favored Go features
- Personal anecdotes and lessons learned