Maybe we have different views of what "changing" means? Every software is different, so take my words with a grain of salt, but personally, if it's always chan

Maybe we have different views of what "changing" means? Every software is different, so take my words with a grain of salt, but personally, if it's always changing its behavior/interfaces/architecture (as opposed to just growing or a healthy mix of both) to me that sounds like either: - It's software that runs with a highly volatile and niche functional target (scrapers, certain bots and business/operation research come to mind). - It's a snowball of technical debt asking for a rewrite that was never given a green light. Sometimes an evolution is needed and then shitlists have a place. If you guide development through shitlists it means you always have shit to get rid of. Maybe you have a ball of shit, in that case?