Something that I would find useful along these lines is: how does a team with a legacy codebase which may not be nice for human in many places pay down the tech

Something that I would find useful along these lines is: how does a team with a legacy codebase which may not be nice for human in many places pay down the tech debt? Most companies have tightly couple code, only partial test coverage and slow build times (builds bloat until the pain is too painful and it is reigned in but that is too far) There is a technical and a social aspect to this. Telling the boss we will ship fewer features etc. as we are doing stuff for future maintainers and better on boarding.