Go Time: Golang, Software Engineering
Technology
A technical dive into how the Go stack works and why we as programmers should care.
Leave us a comment
Changelog++ members save 6 minutes on this episode because they made the ads disappear. Join today!
Sponsors:
Featuring:
Show Notes:
Something missing or broken? PRs welcome!
Timestamps:
(00:00) - It's Go Time!
(00:35) - Sponsor: Tailscale
(04:12) - Meeting our guests
(05:45) - Growing lilies
(10:05) - Starting at the basics
(14:13) - Sponsor: Changelog News
(15:23) - When does the stack shrink
(17:59) - Working backwards with memory
(23:38) - Can you be good enough?
(35:59) - The stack vs the heap
(43:10) - When to care about the heap
(56:26) - Measure first, optimize after
(1:00:53) - Unpopular opinions!
(1:01:10) - Yarden's unpop
(1:05:08) - David's unpop
(1:10:24) - Wrapping up
(1:11:30) - Outro
Your ultimate guide to mastering Go
Migrating from PHP to Go
What if Google lays off the Go team?
Go workshops that work
What's new in Go's cryptography libraries: Part 3
Local cert management for mere mortals
Ship software, not code
The magic of a trace
Debugging
Questions from a new Go developer
Jumping into an existing codebase
How long until I lose my job to AI?
Creating art & visualizations with Go
Foundations of Go performance
Gophers Say! GopherCon EU Athens 2024
What's new in Go 1.22
Go Capture the Flag! 🚩
300 multiple choices
All about Kafka
What's new in Go's cryptography libraries: Part 2
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Lex Fridman Podcast