Can you hear these things around your project?
Every time we decide to improve our practices or technologies, our project becomes more out of date. Every case of the prior, deprecated practice or technology is now wrong. Fifteen minutes ago, it was best practice. From this moment forward, it's legacy code.
A natural enough urge when grappling these problems is to decide "we'll document our current accepted practice, and make sure that new code follows it." Unhappily, when we try to make this work, we find that it becomes something like:
This course is intellectually difficult, expensive in effort, aggravating, and bound to fail. We wanted to find a tractable technical/awareness nudge to take the place of such a heavyweight bureaucratic labor.
Swept lets the team define what obsolete code looks like, and what the recommended changes are.
Change rules can point to external references:
As developers edit files, a Visual Studio Addin shows a to-do list of issues found in the currently-edited code.
(upcoming) Command-line triggered project statistics reporting
The team still needs to decide how they want to behave, given this information.
A team just finding its feet may be satisfied if no new cases of a difficult problem can appear in the code.
A team grown into this practice might