So this is not just about reducing cycles and network calls, but also about increasing the longevity of software and hardware. From a software point of view thi

So this is not just about reducing cycles and network calls, but also about increasing the longevity of software and hardware. From a software point of view this means core quality attributes: performance, security, maintainability. As a web developer I feel we _want_ to focus more on these things, as they are interesting and rewarding, but from a business perspective we typically see them as costly, secondary thresholds that we need to achieve, rather than primary targets. Mechanical sympathy needs time to design, think, learn, measure. Stable, maintainable software needs testing, analysis, refactoring. Again, these are all things pretty much every intrinsically motivated programmer likes to do. But with everything related to resource distribution: People only start to pay for things when the external pressures are already there, or when its too late.