that's because they are doing software "for other humans" - aka, their manager and PM, who gave them the requirements.
So the problem is not the software engineer, but the person who creates those requirements to be fulfilled.
Don’t get me wrong - it has it’s place, and if everyone always tried to understand everything, there are a lot of organizations and situations it would be crushing - but it’s also very frustrating in many situations for those who want high quality products.
It’s the ‘not my job’ syndrome, essentially.
I think what your post’s parent was pointing out is that in lots of environments, such myopia is just an engineers job definition, for which they will be punished if they stray. Interpreting end-user needs is someone else's job.
That's what they're supposed to learn from that, IMO.