Go Time: Golang, Software Engineering cover image

What's new in Go 1.20

Go Time: Golang, Software Engineering

CHAPTER

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
Play full episode

Remember Everything You Learn from Podcasts

Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.
App store bannerPlay store banner