Introducing your team to Go (Go Time #151)

Changelog Master Feed

Can’t find a job working in Go? Perhaps introducing your current team to Go is the solution. In this episode we talk about how Go was introduced at different organizations, potential pitfalls that may sabotage your efforts, some advice on how to convince your team and CTO to use Go and more.

Leave us a comment

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

Sponsors:

• DigitalOcean – DigitalOcean’s developer cloud makes it simple to launch in the cloud and scale up as you grow. They have an intuitive control panel, predictable pricing, team accounts, worldwide availability with a 99.99% uptime SLA, and 24/7/365 world-class support to back that up. Get your $100 credit at do.co/changelog.
• Retool – Retool makes it super simple to build back-office apps in hours, not days. The tool is is built by engineers, explicitly for engineers. Learn more and try it for free at retool.com/changelog
• Pixie – Pixie gives you a magical API to get instant debug data. The best part is this doesn’t involve changing code, there are no manual UIs, and this all lives inside Kubernetes. Pixie lives inside of your platform, harvests all the data that you need, and exposes a bunch of interfaces that you can ping to get the data you need. It’s a programmable edge intelligence platform which captures metrics, traces, logs and events, without any code changes.

Featuring:

• Chris James – Twitter, GitHub
• Mat Ryer – Twitter, GitHub, LinkedIn, Website
• Jon Calhoun – Twitter, GitHub, Website

Show Notes:

• Learn Go with Tests by Chris James
• Go By Example
• Go Jobs posted on Twitter - A Twitter account mentioned in the Gophers Slack during the episode.
• Inception (movie) - Mat jokes referring to the movie briefly.

Something missing or broken? PRs welcome!