This is something a bunch of devs growing closer to us ops-guys have learned as well: Dependants are drag. Infrastructure and central systems stop being agile and nimble if enough stuff depends on it. Trivial changes become really hard.<p>Like, if you have your service with a backend and a frontend and want to toss your API between those out and deal with it, who cares? Do it.<p>If you want to throw out some weird edge case in a base template because "It's ugly", you need to look at 20 legacy services, and 20 somewhat modernized services people don't want to touch, and some 50 more services if they use that. That's the work necessary to understand how much work that change would mean. At that point, we're not talking about executing the change, or reverse engineering arcane mysteries.<p>I'm not going to say it's glorious work, but it makes a roadie or an admin proud if you can keep the "wonderful star" afloat and change everything below it without anyone noticing.