I call them "coders"
They call them programmers. Whatever you call them - not good :)
I don't think I was ever a programmer - I would like to think I was always a (database) Developer. At least according to their metrics.
I remember way back when, I decided to go for a Masters in Information Science. I was attending George Washington University and George Mason. In addition to being taught absolutely nothing relevant to real work (although I did learn to write a compiler in Lisp - very interesting...) as it applied to me - I had to listen to a professor explain that "there is no such thing as a programmer/analyst" (the job title in vogue at that time for developers). His theory was "there are analysts, they do not write code, they architect solutions, then there are coders, programmers - they take this perfection and make code from it". I didn't agree then, I don't agree now. He thought anyone that thought they were a programmer/ analyst was a really bad coder that couldn't think right.
Now, I'm not saying that 19 years ago, I was a really good "analyst" (what we call architects these days). But I really disagreed with the thought that a developer could not be both a "writer of code" and someone with some smarts business wise - who could "architect" the system.
And I still do - see that link, makes a good read. I think they got it mostly right.
Software engineering, not yet a true profession, places no minimum standards and requirements upon practitioners. Until that changes, hobbyist programmers will remain free to masquerade as software development professionals.