While good-intentioned, a lot of these don't go far enough into solutions For example, the "Don't Rearrange the Furniture" section advocates leaving the struct

While good-intentioned, a lot of these don't go far enough into solutions For example, the "Don't Rearrange the Furniture" section advocates leaving the structure of an existing codebase in place. But plenty of codebases have been cobbled together with hacks or short-sighted decisions that end up complicating the entire implementation. So what do you do? You can't leave things alone. Otherwise you're not doing your job. But you can't usually just go in with a wrecking ball either because it could be too disruptive The people skill here is in communicating the problems with the team, working with the team to carve out a reasonable path forward, and getting buy-in from management to implement and roll out the changes by explaining the value that those updates will bring