I don't like the word "professional" in these sorts of cases. I reserve that word for people with formal training and in a job that requires licensing, has a formal code of conduct (lawyers, doctors, civil engineers), and requires continuing education. I see "programming" jobs as just the opposite. A lot of people don't have formal training in the area of their work. Programmers don't have to be licensed, and there certainly isn't any agreement on standards of work or quality. Programmers don't even have to keep up with the times and technology: there are plenty of people out there perfectly content to keep plugging away with COBOL on mainframes (although that number dwindles as people retire).

I also tend to think the people with Computer Science degrees are not formally trained in programming either, but that can vary based on the program they are in. My degree is in Physics, and I went to school with a lot of people who thought since they were smart enough to have a degree in Physics that they could design a bridge or build a tower. Sure, we know all about torques and forces and whatnot, but its not that same as engineer who knows all about concrete and load and technical drawing. The broad theoretical topics like Physics and Computer Science do not necessarily translate to the applied topics like engineering and computer programming.

In my mind, programming is one of the things you learn after you've had the formal training. You study a lot on your own, and you sit next to wise people who teach you things. You read a lot, and you try a lot of things on your own. That's where things start to separate people.

I know a lot of people who have programming jobs, but they do the same thing every day, and they use the same tools everyday. They got into programming when they thought it was a cool lifestyle, that's the job they got, and now that's their career because they are invested in it and don't want to start over (retirement plans, house payments, whatever). They show up on time and go home on time. They learn what they need to accomplish their task. That's not a statement of the quality of their work, just that they have their day job and that's what it is. They do their job, and that's it.

On the other hand, there are people who learn just about everything they can, are trying all the new tools, learn several languages, and read about programming ideas even if they are demonstrated with another language. These people have to take long vacations because after three days in the Caribbean they are still think about their work (or take a GeekCruise and never stop thinking about it). These people would program even if they didn't get paid. They might have a formal education in some area, but not one dealing with technology. They know how to read and they do. They talk to a lot of people and learn their wisdom.

Now, having said that, I'm don't have formal training in programming, but I'm not exactly self-taught either. I know how to learn things on my own, but I've also had a couple of good mentors and have surrounded myself with really good programmers.