For sure. Unlike most developers these days (or so it seems), I've been at my company for nearly a decade. Started out as engineer 15 in a company that is now a

For sure. Unlike most developers these days (or so it seems), I've been at my company for nearly a decade. Started out as engineer 15 in a company that is now a couple thousand. I've seen services transfer teams, get forgotten about, be rewritten, and just about every permutation in between. The way we mitigate this is by tracking the service ownership by team and audit repos from time to time. Every running service is required to have a runbook/playbook that should be thorough enough that a new team member could fix something broken. The biggest problem I've seen is some teams being afraid of really digging into a legacy service if it is transferred to them.