Language goals such as expressivity, readability, brevity, composability; and features such as static typing; and patterns such as monoliths and microservices, ship-fast-fix-later, agile and waterfall design, centralized vs distributed; and aphorisms such as DRY and YAGNI - can be evaluated in the framework of shifting cost between original programmer, future maintainer, service provider, service user, or library/module reuser (and one individual may assume all of those roles at different points in the software’s lifecycle!).