"Silly" probably wouldn't be the word I'd have chosen, but it's a good point. If I'm building a system, I want it to be quality work, and I don't want the programmer who has to deal with it in 2 years to be cursing my name :). Thus I sometimes become very concerned with things that seem to have "no business impact".
I think it might be more of a perspective difference than a language difference. My point was that there is often internal quality work that seems to have "no business impact". This obviously doesn't apply to the example you gave, but the truth is product managers and developers are often looking at two different "products". And there you're especially right on the mark. Programmers need to feel ownership over the product they created, which is not the user experience, but the code.