Well, if you want to get ridiculously technical, we shouldn't use "coding" for anything higher-level than assembling bytecodes at the machine level. The term was in common currency at least as early as Wheeler's "The Use of Sub-Routines in Programming" (1952), while by 1954 the term "automated coding" was being used to describe the use of higher-level languages such as Hopper's A-2 or IBM's Speedcode (and, indeed, even basic mnemonic coding and relative/symbolic address transformations that underlie what we today call "assembly programming").

As it is, I'm comfortable using the term to denote any activity that programmatically and logically instructs a computer to take a certain sequence of actions. C? Coding! Java? Coding! JavaScript? Coding! CSS? Coding! Excel columns? Coding! Ctrl-h and a regex selector? Coding! It's coding all the way down!

Seems fine to me. My dad started programming in the late 60s. I've been doing it for money for 25 years. He says "coding" as a catchall term, and so do I. At some point words get new meanings.

It's just a word denoting a process. Sub it with 'writing a sophisticated software' if you like.