To add a bit.. the gist of the broken windows theory is that the world (environment) evolves even without you or me. A broken window is an action demanding a reaction. If no reaction is taken, "doing nothing" will be read as the reaction. I think that's fascinating!
There's also the same analogy to refactoring in software engineering. If a project is well maintained with every incoming feature, then a big refactor epic won't be necessary.
"The stop of encouragement will prevent the start of discouragement" doesn't mean that the reverse is true ("the start of discouragement will promote the stop of encouragement"). So it isn't stating basically the same thing.
The big irony in social studies with the broken windows theory is that discouragement often feels easier to practice than maintenance to an outsider. Or, in analogy to software engineering, a one time big refactor feels easier to do than continuous maintenance, as all the work actually included in a refactor (team syncing, product without features etc.) is mostly overlooked during the development if maintenance is not well practiced.
There's also the same analogy to refactoring in software engineering. If a project is well maintained with every incoming feature, then a big refactor epic won't be necessary.
"The stop of encouragement will prevent the start of discouragement" doesn't mean that the reverse is true ("the start of discouragement will promote the stop of encouragement"). So it isn't stating basically the same thing.
The big irony in social studies with the broken windows theory is that discouragement often feels easier to practice than maintenance to an outsider. Or, in analogy to software engineering, a one time big refactor feels easier to do than continuous maintenance, as all the work actually included in a refactor (team syncing, product without features etc.) is mostly overlooked during the development if maintenance is not well practiced.