Yes. Because that's a team job. Even if you are working back-end, far away from nit-picky users, you still need to write APIs, and empathise for fellow engineers who are going use your APIs.
I don't distinguish these terms. I distinguish "coding" from "programming/engineering" though. I consider programming to be a lot of things.
Even in relation to coding though, it seems there is an opinion here, that we must be empathic for the future coders reading our code. Do you agree?
A bit of an romantic here, where I think that software is a kind of literature that is meant to be shared and read by other people to learn. It written in a way should be readable to human.
I distinguish "programming" from "engineering" probably the same way you distinguish "coding" from "programming/engineering". When I'm designing formulas for spreadsheets, I feel like I'm programming, but I hardly feel like I'm engineering. Personally I feel that engineering is a level up from programming and requires another set of brain muscle to think about not just creating a solution to a problem, but also creating a robust yet malleable solution that lasts. I'd even imagine how the software might need to evolve over time as requirements change, years later, and the person who's updating the code is probably not going to be me, and what if it's a junior developer? I need to plan the architecture, design the APIs, and document the system in a way that's easy for anyone to contribute.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.