2min chapter

Go Time: Golang, Software Engineering cover image

How can we prevent legacy from creeping in?

Go Time: Golang, Software Engineering

CHAPTER

What Are Some Questions That You Would Like to Ask?

I think people run for micro services, or for kotka, or for some new, flashy tech. But it's like sit down and actually think, like, why don't you like working as good? Why have we had to declare ruptcy on this code base? A thing that i have done that has hilariously sometimes wound up with me not actually abandoning old code basis when i really wanted to. Because, like, the problems i wanted to fix, i could just fix in that old code base. So why make a whole new one with all new problems? It is slightly more nagid thanthe people who don't have that context, they knoww and i

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