alt Hacker NewsGood, you achieved a 10% speedup for a particular workload that some users said they care about. But how do you find out that was really the feature that should have been built next? How do you prevent adding badly factored code? How to make sure you don't pile on top of existing tech debt in the codebase, that you are solving the most fundamental issues first?
> some users said they care about
But how could they possibly know what they should care about if they don't understand the code?
> how do you find out that was really the feature that should have been built next?
Phew right they don't know. Only the devs understand what software should do.