I should add, "coding" is huge oversimplification.
You have to work with the product manager to help decide what the product is going to do. In the planning stage they'll want time and risk estimates for new features or bug fixes. Can we do X? How long will it take? How easy will it be? How likely is that to cause issues elsewhere? What will it take to test it?
You have to understand the existing software and the environment it runs in. Part of this phase is being able to understand what the underlying motivations are, so you can say,
"What you have asked for would be tricky, extensive work, but why don't you do Y which achieves the same and will take a week?"
Depending on what you're making, there may be design and security reviews.
Once you get to implementation, you add to the automated test suite (...if it's widely used, vital software... testing arrangements for something that sells 5 licenses a month may be rather looser!!). Tests to prove it has the required functionality. Tests to prove it deals gracefully with error conditions. Tests to prove it is fast/responsive/copes with high loads.
Meanwhile colleagues will be reviewing your work and you will be doing the same for them. It is not true that you don't need people skills :) It is quite normal to say things like, it's fine but you need to do these 30 changes to the beginning, the middle, and the end...!
Other colleagues may be working on the same stuff simultaneously, so you have to integrate your changes and theirs and not break anything.
"Your" bit may link up to another team's bit, so you'll be schmoozing people in that group to coax vital info out of them so you can crack on.
During the later phases of production, you're responding to problem reports. Often incoherent, hard to reproduce on your computer (but happening all the time to the unfortunate beta tester), or exposing a gap in the implementation. You might be working on entirely new stuff but it's not unusual to be adding bits to something where the original people who worked on it have left, retired, or died.
And you may end up on a customer site, trying to find out what has brought the vital package you sold to Huge Client to a standstill...while fielding questions from them every two minutes.
"Coding" - is the least of it!!!