3 ms·
It's definitely true that they don't care directly about it, since they aren't exposed to it at all, but I would say they care transitively about it, as the dec
by skaushik92 4y ago
It's definitely true that they don't care directly about it, since they aren't exposed to it at all, but I would say they care transitively about it, as the decisions made to build systems impact the reliability & performance of the product, and its ability to be maintained and improved. I've seen too many products that start of usable but due to maintenance issues end up becoming bloated to the point where a sleeker competitor comes along and solves those problems for me.
- nextaccountic 4y agoYeah I was going to say something along those lines. End users care about features and code quality, but not in the way developers think. Users deeply care when their application keeps crashing (but they don't care at all when it doesn't crash) Likewise, users care when the app is too slow, too. And, they care about the app having all the features they want or like (even if they don't know it and can't articulate to you exactly what they want). Users don't care how maintainable the code base is. Whether a new feature takes 2 hours or 2 weeks to make is completely irrelevant for them. Now, they care about the second orders consequences of this: an unmaintainable mess will probably never have all the features they want, or will be too buggy, etc. But, code quality is just a lever to achieve the things that users want. It's a means to an end. If you don't pull the lever correctly, it's wasted