Agreed. I've said forever that I spend one month a year coding, and 11 months debugging, testing, documenting, negotiating, packaging, releasing, supporting.
There's been academic studies on this. The average hourly productivity as measured in lines of code for professional developers is very low. Along to order of 1 to 2 lines of code per hour. This is because of all the other communication and synchronization that you mentioned that needs to happen.
That's a decline. It was 6 instructions per hour when Brooks wrote "The Mythical Man-Month" in 1975.
New languages are so much more expressive.
Would a line not contain more than one instruction, on average?
There are also those times when I write something that technically works in 45 minutes, but it’s 40 lines, but spending another hour or two on it gets it down to 4 lines. The shorter my code, the longer it takes to write. But it’s easier to read and maintain, while also running faster.
This is one reason why lines of code is a poor measure.