When developers are unwilling to add operational features, one option is to write the features yourself. This is a bad option for two reasons. First, the developers might not accept your code. As an outsider, you do not know their coding standards, the internal infrastructure, and their overall vision for the future software architecture. Any bugs in your code will receive magnified blame.
This book makes the assumption that debts and ops are separate. It also implicitly points out some of the key benefits of not making this split. I guess the audience usually selects itself
