[gaylemcd]

Yes, that's fair. If you define "programmer" strictly as someone who currently holds a job title of "software developer", then sure, I'm not a programmer. Nor is, by that definition, a technical founder who's built their entire website. If that's the way you define the term "programmer", then sure, I'm not a programmer.

Of course, if you define it in the sense of what someone can do, has been employed specifically to do in the past, and continues to do as a core part of their job, then I am a programmer.

But, again, that's not relevant to the situation being described. The situation being described is not someone offhandedly saying that I'm not presently employed as a programmer, or asking about why I'm no longer a programmer [by some definitions]. You, and many other people, are creating new situations and saying "well if someone said X after you did Y, then it's totally reasonable." That's not the situation being described. It's the straw man fallacy.

I am describing a specific situation in which someone listened to a talk about data structures, algorithms, big O time, etc (yes, within the context of interviewing) and saying "So when you WERE a recruiter at Google, ...".

The information on my website is entirely irrelevant.

[danielrpa]

I didn't refer at all to the event, despite this thread being about the event. I was just making a point about the possibility of you not being seen as a "programmer".

Possibly I wouldn't characterize you as a recruiter or a programmer based on what you described.

I've been a development manager for many years and programming is an integral part of my role. But I'm a manager, not a "programmer", since I believe it's the dominant aspect of what I do.

So that choice of words could have been more influenced by a possible emphasis on the interview aspect of your role, rather than its programming aspect. I haven't seen the discussion so I can only speak from what I've read.

I've known many hiring managers who were not programmers and knew all of what you mentioned. Some of them were even program managers with a strong CS background - none of them programmers by any definition since they didn't program at all, ever.

[gaylemcd]

So you're imagining a totally different situation and then saying that, in that situation, it might be reasonable to call me "not a programmer." I really fail to see your point. It sounds like you're trying to do this to argue against gender bias being real. This is what's called "straw man fallacy."

If I were arguing that every single time that I'm called something other than programmer that there is gender bias, then your point would be valid. But I'm not arguing that.

[danielrpa]

I'm not trying to argue against gender bias. Gender bias is very real and I've seen it many times. As I've seen age bias, ethnic bias etc. These are real and I have been target of bias myself.

All I'm saying is that I haven't seen evidence in what I read that would strongly indicate gender bias in this instance. You are making the claim so you have the burden of proof. I'm just stating my skepticism regarding your presented evidence.

The best way for bias to be taken seriously by others is to only claim bias when the case for it is very clear. This helps combat people who say that "anything today is considered bias".