| • Introduction to the podcast and its guests
|
| • Guest Cory LaNou's background and community efforts
|
| • Discussion on writing Go code for launching fireworks
|
| • News discussion: Go 1.6.2 update, http2 defaulting to true, and GopherChina conference
|
| • Performance optimization strategies in Go, including:
|
| + When to consider performance (at the beginning vs. after bottlenecks occur)
|
| + Approaches to profiling and benchmarking
|
| + Importance of prioritizing performance issues based on product requirements
|
| • Goroutine unbounded issues in Go
|
| • HTTP router benchmarking and micro-optimization
|
| • Go projects, including the Go Micro Framework and Go kit
|
| • Microservices architecture at Influx
|
| • Communication between services using Protobuf, gRPC, or HTTP
|
| • Trade-offs and challenges of implementing Microservices
|
| • Discussion of Microservices and their implementation
|
| • Debugging issues with network protocols (RPC)
|
| • Announcement of new doc tool "GetDoc" for Go 1.6
|
| • Cory LaNou's experience with open source development and his talk at GopherCon India
|
| • Fear and process of contributing to open source projects
|
| • Discussion of camel riding experiences in the desert
|
| • Command line vs UI tools for Git
|
| • Importance of understanding Git reference logs
|
| • Dangers of deleting and re-cloning repositories
|
| • Benefits of contributing to open source projects, even with limited skill level
|
| • The "Help Wanted" label on GitHub for finding beginner-friendly contributions
|
| • The value of learning by doing and getting feedback from others through pull requests
|
| • The difficulty of understanding complex code, such as the Go raft library
|
| • The importance of domain knowledge when reading source code
|
| • Strategies for learning from code, including starting with the Go docs and then reviewing the code
|
| • The value of community involvement in software development, particularly in the Go community
|
| • Ways to get involved in a local Go community, including attending meetups and contributing online
|
| • The importance of volunteering and helping out with events and projects beyond just coding
|
| • The importance of having multiple people involved in organizing meetups, including a host, sponsor, and organizer.
|
| • Reaching out for help when needed, rather than trying to do everything alone.
|
| • Organizing regional conferences, such as the GothamGo and Gopherfest, and the need for more regionals.
|
| • Starting conferences, with Brian and Erik offering advice and guidance to those interested.
|
| • The value of community members traveling to participate in and help with meetups outside their local area.
|
| • GopherJS team thanked for helping with frontend code fear
|
| • Haxor News: a command line tool to access Hacker News without browser distractions
|
| • Vim Go: praised as essential tool for Go development and Vim users
|
| • Kubernetes: touted as game-changing technology for container orchestration
|
| • Open source community shoutouts, including Patreon support for Vim Go developer Fatih |
