I'd go more with their last statement of, > The team currently in charge needs to have full ownership and be responsible for the code, even if they didn't writ

I'd go more with their last statement of, > The team currently in charge needs to have full ownership and be responsible for the code, even if they didn't write it. That's honestly a high enough bar — many orgs I've worked in do what I call "zero-staffing", which is where an in-use / deployed-to-production project has no team, no engineers (or so few engineers, such as one, as to be a pittance). That one eng, if they even exist, is often just trying to hold everything together. There's a middle ground, of course: an engineer who has accomplished too much might be underwater with questions, but at the same time, they need to pass the torch to the next team that is maintaining it. … but too often, there just isn't a next team. People get burnt out, leave for greener pastures, and stuff gets decommed (maybe) because people are like "what even is this?" b/c the knowledge has walked. The industry is not rewarding experience or knowledge at the moment, so that trend will continue.