You know when users complain about the lingering bugs, unexpected slow downs, and slow delivery of new features caused by tech debt (even though they don’t know that). That’s them caring about your stack, whether they know it or not.
I would say, it’s them caring about the product and their needs, rather than the underlying stack.
I would say you can’t separate the two. It’s a natural extension of Gall’s Law, the simple system that works is the stack.
tbh I’m confident I can deliver bugs, slowdowns, and tech debt using any stack 😎
But that isn’t caring about your stack beyond that your stack isn’t shit.
What truly makes a difference for users is your attention to the product and their needs.
This is the most important thing here. Additional thing to consider that in my experience devs regularly overlook: how easy is it to implement and support?
