Nice post! Your analysis is quite clear and I think you make many reasonable points. I'd like to add a couple of thoughts on this portion:
If you ask a lot of people what their definition of a programmer is, you’ll likely get a lot of responses that boil down to “someone who writes code”.
This is definitely a common misconception. It's useful to make the connection that this is actually closer to the definition of a coder, which is where the confusion comes from.
I think we can generally consider coding to be a subset of programming, which can be considered a subset of computer science. In my experience, programming usually has a lot more problem solving than coding and it's a much broader concept, as you discuss in your post. To put it in numbers, I'd estimate roughly only 30-40% of programming has to do with writing code, while the rest has to do with determining what code (and the structure of the code) to write to achieve the result we want, through a plethora of methodologies.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice post! Your analysis is quite clear and I think you make many reasonable points. I'd like to add a couple of thoughts on this portion:
This is definitely a common misconception. It's useful to make the connection that this is actually closer to the definition of a coder, which is where the confusion comes from.
I think we can generally consider coding to be a subset of programming, which can be considered a subset of computer science. In my experience, programming usually has a lot more problem solving than coding and it's a much broader concept, as you discuss in your post. To put it in numbers, I'd estimate roughly only 30-40% of programming has to do with writing code, while the rest has to do with determining what code (and the structure of the code) to write to achieve the result we want, through a plethora of methodologies.