I suppose one could apply any of those definitions. What I was hoping to express is that there's no upside for anyone, in any of those positions, to internalize the message of "you're not a real programmer."
At best, the message would be tautological. If you tell the accountant with her macros and VBA that she's not a real programmer, because if she were, then her job title would be "programmer" and not "accountant," her response would probably be "uh, okay, I suppose you're right, but you probably didn't need to say that out loud." But, whoever is telling her that probably isn't simply a set theory buff that enjoys a little stating of the obvious, but rather someone being snide to her about what she's doing.
In the end, I think the question of "what makes someone a programmer" is an interesting one in a world where a lot of knowledge work will include at least little bits of automation. But I think the question "what makes someone a real programmer" is a much less productive one, because I don't think people using that terminology are looking for definitions as much as they are looking to feel superior to people.
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.
I suppose one could apply any of those definitions. What I was hoping to express is that there's no upside for anyone, in any of those positions, to internalize the message of "you're not a real programmer."
At best, the message would be tautological. If you tell the accountant with her macros and VBA that she's not a real programmer, because if she were, then her job title would be "programmer" and not "accountant," her response would probably be "uh, okay, I suppose you're right, but you probably didn't need to say that out loud." But, whoever is telling her that probably isn't simply a set theory buff that enjoys a little stating of the obvious, but rather someone being snide to her about what she's doing.
In the end, I think the question of "what makes someone a programmer" is an interesting one in a world where a lot of knowledge work will include at least little bits of automation. But I think the question "what makes someone a real programmer" is a much less productive one, because I don't think people using that terminology are looking for definitions as much as they are looking to feel superior to people.