Definitely fun to think about things in new ways!
This sounds a lot like moving from technology first (layered) design that typically address the same (usually incorrect) challenges repeatedly ('lets build a web app that...', 'lets build a mobile app that...'), towards domain driven design that first identifies the customer domains where solving challenges add value, and separates those using appropriate isolation from the supporting technologies (like web/mobile/batch, persistence...), so we can deliver the same customer domain solution in multiple ways.
In my mind it's applying DRY at the architecture stage.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.