I think this is mostly related to feature-creep and the feeling that developers should do something, even though the product might be "done" (considering that s

I think this is mostly related to feature-creep and the feeling that developers should do something, even though the product might be "done" (considering that software never is quite finished, reading done as "problem solved"). I'm working on a web analytics tool that helps "normal" folks to understand what's going on [0], and users are already starting to demand more than the tool was supposed to be. It's really tempting to keep changing stuff for the sake of feeling productive, instead of improving what's there and making it as reliable and stable as possible. GA is meant to fit all, but it fails on simplicity (alongside privacy and other Google typical problems). This doesn't mean innovation should stop, but I think a lot of software doesn't need to change this rapidly to stay relevant. Docker is another example that struggles to find a monetization model because they basically solved the problem with the first version, and added tons of irrelevant features and services around it. I'm 28 btw, having the same feeling. [0] https://pirsch.io https://pirsch.io