2min chapter

Go Time: Golang, Software Engineering cover image

A deep dive into Go's stack

Go Time: Golang, Software Engineering

CHAPTER

How to Optimize Your Code for a New Version of Go

I think I would definitely use it in the way that I also use coverage testing. You don't want people just kind of looking at some random function that gets called once and being like, let me make sure it doesn't put anything on the heap. Is it possible that we optimize our code and then a new version of go comes out, which makes some changes that then makes our code less performant or makes some of our optimizations unnecessary? Is that possible to happen? He, I mean, I would never say never. Just said it twice, David. I did. Well, that raises really good point, which we do mention this a lot, which is measure first and optimize after

00:00

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode