You’re assuming that the only way developers communicate is through code.
But it’s not. If you want your message to be understood, and the listener is making a good-faith effort but doesn’t get what you’re saying, the onus is on you to communicate in a way the listener understands.
This is a popular claim on HN that I don't think is true. Where does the boundary end? Is it my fault they can't understand my program if they don't know any code at all? What about if they're a Python programmer hired onto a Java project? The point is you should make a good faith effort to write readable code, especially for your team members, but you're a programmer, not a teacher.
>Lack of empathy also leads to disregard for the needs of users and future maintainers.
This I agree with. Its a very underappreciated reason to build empathy as a programmer.