AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
2min chapter
What's new in Go 1.20
Go Time: Golang, Software Engineering
How to Deprecate a Decision Record
A good old decision record says, okay, we're going to go this way because reason is X, Y, and Z. One of the things I've started doing is also including there, when will this solution no longer be applicable or required? When do we deprecate this? Right? What must be true in order for this to no longer be needed or wanted? Because if you're going to make compromises, right? If you're Going to make a trade off, when you no longer need to, right? It would be nice if you can remove that from your codebase.
00:00
Transcript
Episode notes
Get the Snipd
podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered
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