Sorry, Neither

I heard the sad news on Sunday of the passing of Nichelle Nichols. I had always been fond of her character Nyota Uhura on the original Star Trek. Growing up in a fairly liberal household and only catching the original series in reruns, I didn’t find her presence on the bridge of the Enterprise all that surprising. It seemed normal. Of course I was young and honestly naïve and didn’t realize until years later exactly how groundbreaking her presence was. This of course was in contrast to a young African-American woman named Whoopi Goldberg.

Well, when I was nine years old Star Trek came on,” Goldberg says. “I looked at it and I went screaming through the house, ‘Come here, mum, everybody, come quick, come quick, there’s a black lady on television and she ain’t no maid!’ I knew right then and there I could be anything I wanted to be.”

That said, there was always a scene from the episode The Naked Time that stood out to me. Lt. Sulu, under the influence of the polywater and in swashbuckling garb, grabs her and says “I’ll protect you, fair maiden.”

Oh my!

Her response, the title of this post “Sorry, neither” is perhaps the shortest quote that stands out from any of the Star Trek series. However, it wasn’t until recently I learned that some folks interpreted it different from me, and I realized they had a point. They interpreted the neither to mean Uhura was declining the protection and demurring against the “fair maiden” part of the quote. And I certainly can see it that way. And I always figured that was part of it. She was quite clear, she was a Star Fleet officer, as highly trained as Sulu, and not in need of any particular form of protection. This perhaps more than anything else I think helps define her position in Star Fleet and Rodenberry’s and her concept of Uhura. She wasn’t a token.

But, over the years I had focused a bit more on the fair maiden part. I’ve often thought the neither was used to negate both parts of that. Let’s be clear, Nichelle Nichols was by any token a fair woman to set ones gaze on and the camera work in the early Star Trek often used softer lenses to highlight the female cast members. But, as Uhura, while she had the voice of an angel as demonstrated in the Episode Charlie X, it again was clear she wanted to be first considered an officer and a competent crew member. Perhaps in off hours calling her fair would be taken as a complement, but on-duty was an insult.

So that leaves maiden. One often associates the idea of a maiden with being virginal and with that again a certain level of helplessness or having others determine ones fate. Uhura was making it clear that she wasn’t virginal, helpless or incapable of determining her own fate. While in the original Series we never really saw any romantic relationships with her, she in a single sentence made it clear she had probably had them and had a say in how they developed and progressed.

In the end, regardless of how you interpret it, those two words spoke volumes. Nichelle Nichols was playing a character who was capable, confident, competent, and had earned her place on the bridge of the USS Enterprise. Since Star Trek, especially then, has always been an allegory to hold up to the real world, Nichelle Nichols in two words seemingly spoke for every African-American out there.

On a more personal level, I had the honor and pleasure of meeting her and with my daughter getting a picture taken together. This was in 2019 and while it was clear she didn’t have the verve she had from her youth and was seated the entire time, her presence was unmistakable. We were standing in the presence of greatness. I was honored to be there.

Hailing Frequencies Closed.

#YesAllMen

For over two years I’ve been wanting to put together a speaking topic using the above as a title or as a subtitle. The reason is because the alternative, #NotAllMen is NOT a good thing to use.

Yesterday I came across an article that said it better than I could. I would recommend you read it first: Buzzfeed Article.

It brings up several great points, including ones I had not given much thought to. Look, I know when a friend of yours is upset that a guy just made a pass at her in a professional setting, one of your first instincts is to think “I’d never do that” and are tempted to say “#notallmen” you’re not being helpful. In fact, you’ve just made it about yourself. Just don’t. That’s not what is needed.

Look, I’m pretty confident that all my male readers are pretty decent guys. I work with many of you professionally, some of you in volunteer positions, some are simply friends, and some readers, I suspect I don’t know, but you’re probably ok too. None of you are outright sexist or racist. If you were, I wouldn’t be associating with you. But all of us are still a product of our environments. We make the off-handed comment without thinking about it. Or someone around us makes a comment and we don’t react. This is also why I suggest when it comes to calling yourself an ally, just don’t.

Several years ago I helped organize and then participated in a Women in Tech panel for our local SQL Server User Group. I was the only man on the panel and expected to be asked what was the best thing I thought we, as men could do. The answer was of course somewhat ironic: “Sit down and shut up.” I of course expanded upon this. No, we can’t nor should we ever completely shut up. That wasn’t my point of course. My point was to make sure not to center the discussion about us. When a friend complains about a sexist incident, replying #NotAllMen is doing just that. Centering the discussion on us. Sorry, that’s a time to shut up and listen.

But when others make sexist comments, that’s a time when it may be appropriate to say something. And if someone calls you out, take it in stride. We make mistakes. And if someone takes you aside and says something (I’ve now heard that called a “call-in”) thank them. It means they think well enough of you to help you be a better person.

At the end of the day guys, we’re all still part of the problem, even when we do our best. That doesn’t make us evil. It simply means we have space to grow into. Let’s do that. Let’s grow.

Reasons I Attend WIT Events

Last Friday, I took time out of my day to attend the Data Platform WIT Day. Hosted on Redgate’s Zoom, it was a series of webinars that started with Rie Merritt’s excellent Keynote Lifting as we Climb and concluded with Stepping Stones from Diversity Learning to Equitable Actions with Cindy Gross. The full list of sessions is available at YouTube here.

I highly recommend you take some time out and check out the sessions that may appeal to you. The keynote is 30 minutes and the follow-on sessions are roughly an hour each. Because of other events on my schedule I wasn’t able to attend all of them, for example I could only jump into Cindy’s about half-way through, but very much enjoyed what I watched and learned quite a bit.

Afterwards, one of the organizers, Mala Mahadevan tweeted the following:

https://twitter.com/sqlmal/status/1367951596227854340

I was caught a bit off-guard by the call-out, but not in an unpleasant way. I’m proud to support WIT. And it prompted me to write this post on my usual Tuesday, just a day after International Women’s Day.

I attended for two reasons: one was for learning and the second was honestly to be supportive.

The first reason should be obvious. There’s some good information in these webinars. Tracy Boggiano gave a great presentation on dbatools and dbachecks, tools that I definitely need to learn more about. The panel on mentoring with Leslie Andrews, Shabnam Watson, Deborah Melkin, Gilda Alvarez, and Deepthi Goguri was a great learning experience for me. I gained further insight into how mentoring can work, especially for those who have a different experience than mine. And while the panel focused more on the experience and value of mentoring for women, I gained several great takeaways. So it wasn’t just a “women for women” type event.

But quite honestly, I attended in part for the same reason I’ve often started using my pronouns in various places (him/his for those who aren’t aware): to normalize the practice. I think it’s important for those who don’t identify as women, and especially for those who identify as men to attend such events. While the focus of a WIT event is for women, it does not mean men can’t learn from it. It doesn’t mean we’re not welcome. I had heard much of Rie’s talk before, since she adopted it from other talks she’s given. It’s primary focus is of course on how women can help women grow in their professional careers. But there are tips that men can learn, such as not interrupting the women they work with, amplifying their voices, and more. I tell the story that the first time I heard Rie speak, I was one of two men in the room, and the other was a friend she had apparently asked to attend in order to give her feedback. I was a bit saddened there were not more men there, as we need to learn a lot of what she has spoken about. I suspect some men felt “oh I don’t need to go” or “there’s nothing there for me.” But they’re wrong and I want to continue to normalize attending such event for those who present as men. And I attended of course because I want my women colleagues to know they have support, that I value their contributions and experiences.

Now that said, I will add that events such as last Friday’s are “Women in Technology” events. The focus is in the name. While welcome, men should avoid any attempts, conscious or subconscious to center them on their own experiences. What do I mean? For one, during the Q&A parts, if you feel tempted to say “I have more of a comment than a question…” just stop. Nope. It’s a Q&A period, not “I want to hijack the discussion and talk about myself period.” This is not to say questions aren’t welcome. But make sure they’re actually relevant to the topic at hand, e.g. “Tracy, I think I missed something, am I correct in understanding that the latest version of dbachecks has a problem with the latest version of Pester?”

So my advice, do your best to be an ally by your actions, not your claims.

And that said, for those who are inevitably going to ask: When it International Men’s Day?

Guy’s it’s on Us

A short thread on Twitter yesterday prompted today’s blog. Dr. Jen Gunter (who I do not follow) mentioned her planned response to “I don’t have a question, it’s more of a comment.

One of the replies I thought completely missed the point and I tried to respond in a somewhat humorous but pointed way to the man replying. It took him about 9 hours, but he finally replied and I think based on his reply, completely missed my point. Oh well. I had tried.

But it got me thinking. Had I been blunt enough? Should I have been a bit more confrontational? Could *I* stand up at a conference and give Dr. Gunter’s pointed reply? And of course, the nagging question in the back of my head, “had I commented when I a question was the appropriate response?” or otherwise ended up “centering the discussion around me rather than the original person?”

Let me address the last first. I’m sure I have. I like to think “well I’m a friendly guy, I like to relate and show I’m relatable.” And that’s all true, but, that’s also part of the problem. It’s a case of recentering a discussion or something around me. I’ve always tried to be conscious of this since college when I took a class at the women’s college down the hill and realized that what I had heard about men dominating discussions was true. In a class of about 20 students, with just 3 men, one of the men (and no, it wasn’t me) clearly dominated the discussion.

Anyway, back to my response. I actually sometimes am jealous of some of my friends who can have “I have no fucks to give” attitude and will openly confront someone like that. I think sometimes that can be a good thing, especially with a more egregious example. And I’ve seen some that are pretty bad.

My attempt to deflect the one tweeter’s reply with a bit of humor apparently failed. So I started to think about how I might handle this at an actual seminar and then I realized I had.

It was at a SQL Saturday a number of years ago. It was a good topic, though, for reasons unknown to me, the presenter has not, to my knowledge presented again. And then there was the raised hand. It was someone I knew. And, he had more of a question than a comment. Then again about 10 minutes later. And I think probably a 3rd time. Now, he was in now way being mean or malicious. Heck, I think no matter how hard you looked, you’d never find a mean bone in him. He’s genuinely a decent guy.

But, and this is what I think we all need to do, after the talk, I pulled him aside and pointed out what he had done. He as embarrassed and apologetic. And he vowed to do better.

And as I write that, I realize, this happened TO me. See, I said I wasn’t perfect and I had failed. This time it was on Twitter. I typed a reply that I meant to be supportive and add a touch of humor. A friend DM’d me, “Really?” At first I was confused, but when I asked for her to expand, she pointed out what I had done. Yes, I had meant well, but sometimes intentions are less important than results or even perceptions. I decided to delete my comment, despite her saying it wasn’t necessary. I realized I had not contributed to the discussion and my comment could be a distraction that wasn’t needed. And since them I’ve tried to be better. But a comment she said stood out to me. She DMd me because she thought I was one of the “good ones” that I’d listen and accept feedback. That meant a lot to me. She could have ignored my comment and let me continue to be a jerk at times, or she could have publicly called me out and humiliated me, which might made her point publicly, but caused me to be hurt and not grow. She took the time. I appreciate that.

However, yesterday’s Twitter thread reminded me that all too often in situations like this, women and other minority (in that environment) group end up doing the emotional labor of trying to keep the discussion from recentering the discussion the “I have more of a comment than reply” crow.

Therefore, I think often the onus needs to be on us men to call out our fellow men to say, “hey, that’s not cool” or “do you realize how you came across there? I know you didn’t mean that.” We can’t rely on women and other minority groups to do all the emotional labor. So if you see someone trying to talk over a speaker, pull them aside. If you hear them make an off-color comment in a meeting, speak up. Call out behavior. Find a method that works for you.

I prefer, but am not always good about doing it, calling our behavior a bit more publicly. Not necessarily to embarrass the commenter, but to hopefully get them to correct their behavior and so that the original speaker knows they have support.

For example, if someone in a meeting makes a comment about “yeah, let the girls over in accounting handle it”, unless this is an accounting class for teenagers at an all-girls school, you can and should say “Umm, you mean the women right?”

You don’t have to humiliate a person to make the point. In most cases, the person doing it may not be aware and simply needs a nudge. Give them that chance like I was given. Now, in the end, there will be a few folks that do need to be simply called out and made an example of. I’m ok with that, but for the vast majority let’s work to give them the nudge.

What’s My Lane?

Yesterday a fellow #SQLFamily member, Brent Ozar tweeted about how someone objected to some content in his latest email he sends out to subscribers. Based on the response, I’m guessing it was this email.

Now, let me back up and in full disclosure say I’ve met Brent once or twice, sat in on a SQLSaturday session of his and one User Group meeting where he presented, but don’t know him well. We’ve never sat down and had a beer or discussed DBA topics together. And, in fairness, my blog on a good day probably gets 1/1000th the reads his blog will get on a bad day. He’s what some might call “a big name” in the industry. He’s an expert on SQL Server and well worth reading for that reason alone. I can’t guess how many people read his blog or newsletter, but I can say it has influence.

And so, someone felt that him writing about something other than how to build an index, or why not to use an update in a trigger was him straying from his lane and he should stick with data related topics. He’s already responded in some tweets and I presume elsewhere but I figured it was a good topic for me to blog about.

As long-time readers know, I don’t write just about SQL or PowerShell, but I also write about cave rescue or marshmallows or Safety (one of my more popular pages strangely). In other words I have an eclectic array of topics. But I also have some themes and I’ve written about (not) being an ally, or gender factors in giving blood. There are others, but the general point is I sometimes also write about social issues I think that are important. I think I’d be hard pressed to say what my lane is here; perhaps it’s more like a curvy mountain road?

But let’s go back to the person who told Brent he should stay in his lane. What lane did that reader refer to? I’m presuming it’s a narrow lane of “topics related to databases”. But, I think that person is wrong and I fully support Brent’s “straying from his lane.” Why? Because of power and privilege.

I’m going to go out on a limb (though I suspect it’s not a very far one) and state that I suspect Brent and I share much of the same privileges simply by being born the gender we are and skin color we have. There are other aspects we probably share.

These innate privileges give us power. And sometimes we are consciously aware of that power and other times unconsciously blind to it. Having the power and privilege itself isn’t an issue. It’s how it’s used that is important.

For example, all too often, I forget that I’m more likely to be taken seriously when I talk about a technical topic than some of my fellow DBAs, simply because of my gender and/or skin color. I can be unconscious to that power and privilege or I can work to be conscious of it. And by being conscious I can try to improve the situation for my fellow DBAs who don’t have my innate privileges.

I can be ignorant of that fact that no one questions my marriage and be oblivious to how some had to wait for the Supreme Court to recognize the validity of their love for their partners. Or, I can be aware of that and support my LGBTQI brethren in being allowed to live with who they choose and to marry them if I wish. This shapes my political opinions and who I will vote for. For example, I won’t vote for someone that I think will act to take away same sex marriage or will enact legislation that hurts such folks.

But there’s also more conscious forms of power. Simply being aware is not enough. Making room for others to be heard is a positive use of power. This is what Brent did and I fully support it. But, he didn’t simply make room, he provided the metaphorical microphone and the loudspeakers. If you didn’t look at the link above, look now. You’ll note that Brent didn’t write the email in question, but rather he gave space to a fellow DBA, Andy Mallon. This wasn’t an accident, this wasn’t Brent being lazy and not wanting to write an email, this was a conscious choice. This is using his power as a well known DBA and “big name in the industry” as well as his privileges to give a voice to others. (Please note, Andy’s a friend of mine, I’ve spoken with him at SQL Saturdays and he’s no slouch, but as far as I know he doesn’t have the audience that Brent has.)

I can support that use of power and if it’s “straying from his lane” so be it!

That said, as I wrote in my article in giving blood, as DBAs, we can NOT simply divorce ourselves from social issues. It’s not as simple as “well I just write SELECT statements and create tables.” The very data we record encodes social standards. When we make gender a bit field, we’re enshrining a very binary view of gender that does not reflect the lived lives of those around us. When we make fields that say Husband or Wife, rather than Spouse 1/Spouse 2, we are saying that only a certain form of marriage is valid (And for that matter, why stop at Spouse 2, why not make it a separate table for the day when someone walks in and claims to have more than one spouse.)

In other words, even if Brent had never strayed from writing about SQL Server, his lane would properly include social issues. Data isn’t nor should it be completely separate from social issues.

And I’ll toss out a few URLs here:

P.S. for those who read my post last week, I’m happy to say I got my slide deck and recording uploaded for presentation at PASS Virtual Summit 2020: PowerShell for DBA Beginners! So join me on Nov 11th at 2:00 PM! And use code LGDISIIK3 and save $50!

Pushing Solutions, not Products

Earlier this week, the governor of New Jersey put out a call for more COBOL programmers. Everything old is new again. Last time I remember such a call was around the year 2000. That said, while I never had the opportunity to learn COBOL, I’m amused by this. It reminds me of a quote I heard in college about Fortran and how one expert didn’t know what language engineers would be programming in in the 21st Century, but they’d call it FORTRAN.

But, I highlight these two languages because the truth is, they are the exception. In reality one has to constantly keep learning. The times, they are a changing as a poet once said. Fortunately for me I’ve been busy during this Covid-19 lockdown, but even still I have free time (some who read my blog may argue too much time!) That said, I’ve been trying to take more time to catch some webinars and to learn new skills.

Over the past few weeks I’ve got a couple of SQL PASS WIT Webinars under my belt. Last week however, I took advantage of Redgate’s Streamed event. (full disclosure: Redgate does pay me for the articles I write for Simpletalk but what I write here is not paid for by Redgate in any way).

There were a lot of great webinars and I did not catch all of them, so please don’t take my lack of mentioning any as a comment on their quality. There were also some I could only listen to partly as I was actually doing work at the time.

First off, I started with Kendra Little‘s session using git for database development. I’m still moving in this direction and it gave me a good insight into what I’m doing right and moreover what I’m doing wrong and how to improve it. I recommend this session to anyone trying to get version control into their database development.

Unfortunately I had to split attention to Grant Fritchey‘s session on learning to effectively use Extended Events (I do have to do billable work from time to time) but did catch some good stuff. Again, if you haven’t played with Extended Events, please do! I recently used them to help debug an issue I was having with a client and their Reporting Server (yes! you can write them for an SSAS instance!) Go Team #ExtEvents.

Andy Mallon’s session on shortcuts for the DBA was excellent and seemed to generate the most feedback in the chat window. I suggest you go to his page and find his print-out for keyboard shortcuts for SSMS. It’ll save you a lot of time. That said, watch the video if you can and see how well Kendra Little did on her “job interview”. (To be fair, I suspect most of us would have done about the same!)

Steve Jone’s session on unit tests was good, at least what I caught of it. Again, client work got in the way. I may go back to specifically watch this one.

After that, I had time to catch Grant Fritchey’s session on SQL Injection. It still amazes me how many programmers STILL write code so susceptible to this. He had a lot of great examples and offered some solutions. Note there’s no single right answer, but there’s definitely a lot of lousy answers.

Friday brought Rob Sewell speaking about SQL Notebooks and using Jupyter. I haven’t used this yet, but it’s on my list for the year.

Again, a great presentation by Grant Fritchey, this time on convincing the DBA to support DevOps. I’m come back to this in a bit.

I think the highlight of Friday was the costumes. In honor of SQLBits which was postponed this year, several of the presenters wore costumes. I think Steve Jones, with his hat, wig, and glasses won in the pure costume category. (You’ll have to check out the videos). But, that said, Kendra took the overall prize with her corgi Freya on her back in a pack. There was just something so wonderful watching her talk about index tuning as she’d casually feed a carrot over her shoulder.

Again there were other sessions and speakers, and even if I didn’t mention them, their presentations were top notch and worth the watch. Again, you can go to: https://www.red-gate.com/hub/events/redgate-events/redgate-streamed/ and catch them o demand. I recommend it.

One of the overarching themes I picked up on was an emphasis on DevOps and using both tools and processes to achieve a successful DevOps environment. Note that I think both are critical. One can have all the best tools, but without good processes, not much will be accomplished. Honestly, one take away I got was I’d rather have good processes and develop my own tools than have tools, but no process. This focus makes sense given Redgates focus on DevOps.  I now in the past I’ve made the mistake of simply thinking of them as a company that sells some cool tools.

I want to close with saying, one thing I appreciate about the #SQLFamily and Redgate does this well, is generally members focus more on solving problems than pushing specific products. I’ve attended more than one webinar hosted by RedGate where other than mentioning them as a sponsor, their name hasn’t come up at all. I’ve seen other members of #SQLFamily do the same thing. They may work for a company that provides tools and solutions, but if you use #sqlhelp on Twitter, you’ll find almost always it’s people there are about solving your problem, not pushing their software or solution.

So that was how I spent part of last week in lock-down. How about you?

P.S. I also made some boule bread to with the homemade chili on Saturday. It was a winner in the Moore House Hold.

 

The Year So Far

Today happens to be the last day of the month and the last day of the quarter. And according to my calendar, it’s the 4th Blursberyday of the month of Holiecouw.

I decided to take a look back at my first post of the year: 2020 in Preview. Wow, a lot has changed in a scant three months. I mentioned I was reading Station Eleven. It’s set in a post-apocalyptic world after a world-wide flu pandemic. Little did I know at the time I’d be living that reality a scant 3 months later. Ok, this is not nearly as bad as in the book, but it does give on pause to think. We are living in a time of upheaval and it will be interesting to see how this current pandemic changes social structures for coming years.

I wanted to speak at SQL Saturdays. Well, almost every one I’ve put in for or was planning on putting in for has been cancelled or delayed. So much for that goal. On the other hand, members of the #SQLFamily have been holding Friday afternoon (and other times) Zoom hangouts as sort of a morale boost. So I’ve actually gotten to know a number of my fellow DBAs and fellow speakers, so that’s better.

Fortunately, I’m still working. As a consultant, you realize every meal may be your last meal, so you keep working at it and hoping more meals are coming your way. So far my biggest client shows no sign of slowing down, nor does my second largest client. I’ve been fortunate, I know a number of folks across many industries who have been hit with a temporary or even permanent job loss. This is going to be hard for many.

But, I’ve also been taking the time to do more webinars. Last week I sat in on a Redgate webinar on the state of DevOps that was quite informative. The next day, Kendra Little (also of Redgate) gave the WIT webinar and also talked about DevOps. Both were quite informative and I learned a lot. I look forward to the upcoming Redgate Streamed event.

I’ve been using git more and more. I started using it integrated with Visual Studio about two years ago I think. But, after seeing my son working on a project where he was using it at the command line, I decided it was time to start to do that and now for one client that’s my de facto way of checking in and out changes I’ve been making to the PowerShell scripts I write for them. Next up, more version control for the SQL Scripts. I’ve already written a small deploy script I use to deploy scripts and changes and more importantly to log them. So while that client hasn’t really adopted DevOps, I’m doing my part for my small corner of work.

My next goal is probably starting to learn how to use Docker more. Cathrine Wilhemson’s blog post on that has convinced me it’s time.

And I finally finished binge-watching Haven.

So, the last few weeks haven’t been exactly what I planned for, and the upcoming months won’t be what I planned on either, but it hasn’t been a terrible time. What about you?

P.S. While out biking the other day, a thought dawned on me. Many post-apocalyptic books (such as Station Eleven) have characters using cars, but more like carts, either pulling them themselves or with horses because once the gas runs out, you can’t make more. But I got wondering how having a large number of electric vehicles would play out in such a world. Yes, much of the infrastructure would be gone, but even if you had to carry panels with you (much like Mark Watney in The Martian) you could probably be far more mobile. Hmm…

Follow-up to last week

As a blogger, often I find myself tracking the number of page views a particular post gets as a measure of success. If I post something and it gets 20 page views and the next week I post something and that gets 100 pages views, one can sort of claim that the second post was 5 times more successful.

But the reality is, that’s probably really only a measure of popularity. One of my most popular posts was about some ongoing issues at RPI. But, I’m not entirely sure that popularity is a measure of success. In fact I’d argue that it’s often a misused metric.

What I actually prefer to know, but is often far harder to measure, is the impact a post or lesson has. I mentioned in an earlier post about how a single part of a lesson during a cave rescue class made a big impact.

So, this gets me to last week’s blog post. In terms of popularity it was rather humdrum. It didn’t stand out much in terms of the number of views it received and I was initially afraid that perhaps no one was reading it. (Yes, as a blogger, I have do have enough of an ego to hope people read my posts).

But, then something strange happened. I started getting comments and feedback, both here and other social media. Most of it was public, but some was sent privately and I’ll respect the privacy of those who sent it. And the feedback was generally supportive and informative and in several cases from women I know and whose opinion and feedback I value.  To them, I want to say Thank You. It is gratifying to know my post was read and had an apparently positive feedback.

I’m going to end this week’s quick blog with the name of a book that I’m reading this year. Yes, I say “this year” for a reason. Headstrong: 52 Women Who Changed Science and the World by Rachel Swaby. Each chapter is a quick read and it helps highlight the fact that women have been changing the world even when we didn’t know it. Some names I’ve recognized: Virginia Apgar for example. Most, like Mary Putnam Jacobi are new to me, but fascinating reads. I’m trying to read one bio a week, hence why it’ll take a year to read. I look forward to reading about Rosalind Franklin for example, a woman that I’d say was pretty much cheated out of a Nobel Prize.

So, in closing, thank you to who commented and gave me feedback. I value it and learn from it. And it makes writing my blog worth it to me.

Oh, and I have to comment on last week’s header photo. I picked it because it was a subtle example of poor design, anyone sitting at that spot on the bench risked having the latch slam into their legs. But I also picked it because I took it before one of the hockey games my wife plays in. She’s the one playing hockey. I’m just the guy opening and closing the door as they get on/off the ice.

I don’t see a problem…

Today is the 3rd day of Women’s History Month here in the US and today is Super Tuesday and we have a bunch of older white men and a two women vying for the Democratic ticket.

And yet, I started my reading with a response on a blog of fellow #SQLFamily member, Monica Rathbun that comes down to “I don’t see a problem, therefore it’s your fault and you should change what you’re doing.”

So I want to go back and talk a bit about privilege. But before that I want to talk a bit about my childhood.  I was fortunate in many ways growing up; a good grammar school, the ability to attend a very good high school and fortunately I got into a great college. That said, my family was never rich and I know at times either of my parents were carefully counting pennies. So in some ways I was privileged in others, not so much.

But that’s not the form of privilege that really mattered.  The privileges I was born with were more intangible and can’t be measured by a bank account or resume. They’re more subtle. But today I want to talk about a specific ones: being a man. This is a circumstance of birth. It would apply no matter where I was born in the US and regardless of my economic situation.

What exactly does this mean? For one, it means I don’t recall thinking much about it until college. Yes, I knew about feminism and discrimination before then. My mother was a divorced woman in the ’70s running her own business. She was (and is) someone I am proud of. But in general, discrimination was something I read about, not something I knew.

But then there was the time I was sitting in the backyard of a college girlfriend’s sorority house talking with her and a friend of ours. Our college, RPI, had a ratio of 5 men for every woman that attended, so again, I knew there were problems. But, I didn’t realize what privilege meant until the friend mentioned that she always submitted her papers to her professors with just her first initial and last name.  I was a bit confused. She explained to me that she found she received better grades when her professors didn’t know it was a woman submitting the papers. I was taken aback. Sure, I knew RPI’s ratio was problematic, but I had always assumed that once a woman got into RPI, that for the most part, she was judged on her merit, not her name. I was clearly wrong. (And honestly, even that’s not quite accurate about not being aware. I had a friend who had dropped out of the architecture program 5 years previous, in part because of a sexist professor).

Now, it would have been easy, even trivial to say, “Nah, you’re just imagining it.” I mean I had never seen it happen. I only had her word to take for it after all, compared to my entire life experience of not seeing it.  Well actually I had her and my girlfriend’s word for it since she chimed in too. I choose to believe them. I also, by the way, started to do the same thing with my papers at times. I’m not sure how much thought I really gave it, but I’m pretty sure I figured the more semi-anonymous papers submitted, the harder it would be for professors in general to catch on that perhaps it was women doing it.

Now, I’m sure some readers (and I’m betting mostly the men) are saying, “yeah right” and since most of my readers are geeks, they’re probably thinking, “show me the data.”  That is somewhat fair. So let’s take a look at a shift in orchestras in the US. Up until 1970, the top 5 major symphonies in the US were predominately male with over 95% of the positions held by men. Now, I’m not an expert in music, but I suspect that women like music as much as men. So, obviously something was going on here.  At some point in the 1970s and 80s, most major symphonies made a minor, but very important change: they put the musician behind a screen during the audition. Now the judges knew nothing about the performer and could only judge them on their music. A surprising thing happened. The number women selected for symphonies increased. Removing the ability for bias at an early stage helped close the gender gap.

So, can I prove my friend’s assertion that removing her female sounding first name helped her grades? No. But can I believe it? Yes! Can I believe she and my girlfriend were victims of bias? Certainly.

So let me go back to Monica’s blog. First of all, if you haven’t read it, please do. In fact, given the choice between reading hers and reading mine, read hers. She’s talking from her personal experience. I’m only speaking as a reflection of that. I also want to add that my hope (and goal) here is not to usurp her voice or the voice of any other members of my #SQLFamily, but ideally to bring them to the forefront.

But for a minute, back to my privilege.  I want to mention a few things that my privilege has allowed me to ignore, often without realizing it.

  • I’ve never wondered, “did they select me to speak because I’m a man?”
  • While yes, at SQL Saturdays I’ve tried to dress professionally, I’ve never given thought to “will someone find this too sexy?” or “will someone tell me I should dress a bit sexier.”
  • No one has ever told me, “you should smile more, you’re more handsome that way.”
  • I’ve never once been concerned with if my technical abilities were being judged on the size of certain body parts.
  • I have never thought, “will that person hit on me after I’m done talking?”
  • I’ve never had a woman monologuing during the Q&A instead of actually asking me a question about my presentation.

These may seem like silly things and you may think I’m making them up, but I can assure you that if you ask the women around you, they’ve experienced at least some of these, if not all of them.

Now like Monica, I’m going to present a few good points. I’m very fortunate to be a member of two great communities, #SQLFamily and the National Cave Rescue Commission. However, let me reiterate that neither are perfect. Sexism and bias exist in both communities and I’ve seen it first hand. But I’ve also seen a lot of efforts in both to recognize folks based on their skills, not their genders.

But we can get better. And here I’m going to talk mostly to the men reading this, in part because I think we have to do a lot of lifting.

For example, I’ve caught fellow attendees at SQL Saturdays doing that monologuing thing. If you don’t know what I mean, try this experiment the next time you’re at a SQL Saturday (or honestly any conference, but this is probably more true at technical ones).  Go to an equal number of speakers who identify as male and female and sit in back. Then start to note what happens during questions. While not universally true, in my experience, when it’s a man presenting, most of the questions are actual questions and typically on topic. But, often when it’s a woman presenting, the “question” is often a monologue of sorts. Yes, often it’s in support of the presentation’s topic, but it’s generally the questioner talking about themselves, not them trying to enrich their knowledge by learning from the speaker.

Learn from your mistakes, don’t double-down. I’m going to call-out Rick here on Monica’s post who doubled-down. Not only did he dismiss Randolph’s response, he tossed in a diminutive of Randolph’s name. Now I’ve met Randolph at Summit and Randolph’s a cool person. But even if I didn’t know Randolph, I wouldn’t use a diminutive of their name without their permission.

Recently, I replied to a tweet of a friend mine who is active in the WIT community.  I thought I was being supportive, but her DM to me was basically, “WTF Greg?” My initial response was equally tone deaf. But, she took the time to explain to me why she found my response to her tweet problematic. Now sure, sometimes it’s a blow to ones ego, “but I thought I was being supportive!” But when the person you’re trying to support says they don’t find it supportive, don’t dismiss them and don’t go off in a huff. Accept the fact that they didn’t find support from your efforts. Take it as an opportunity to apologize and to grow. And think of it this way. They had a choice. They could have ignored you completely, or called you out in public and possibly shamed you, or take the time to pull you aside and educate you.  I’m grateful she took her time for the last option.

Almost finally, if you’re reading this and still thinking that gender bias isn’t an issue, or you’re thinking, “but none of the women I know have mentioned this to me” stop and think about it. Maybe they have and you’ve been oblivious or ignored their experiences. Or, and this is perhaps worse, they haven’t mentioned it to you at all. If not, you might want to wonder why.

Finally, as I’ve said, I don’t like to call myself an ally. I’m honored when others consider me such and I strive to me such. But, as I noted before, I’ll make mistakes. I can’t promise to be perfect, I can only promise to try my best and to try to learn from the experience of the great women around me.

P.S. If you do dismiss the experiences of my colleagues, in #SQLFamily or NCRC, please don’t bother attending my talks or discussions.

P.P.S If I ever fail, call me out. I’m continually striving to be a better person.

Hampton Roads User Group Recap

I’ve talked about how I think it’s important to be part of the #sqlfamily community and how I enjoy talking and giving back. Last week was another example of this. Much earlier this year (it might have even been at Pass Summit last year) I convinced Monica Rathbun to do a quid pro quo. I’d speak at her user group in Virginia Beach if she’d come to upstate NY to speak at my user group. I’d seen Monica speak and knew she would be a great speaker for my group. Fortunately, despite seeing me speak, she apparently felt I’d be good enough for her group.  Seriously though it was a good deal.

My original plan had been to drive down Wednesday, address her group, stay at an AirBnB on the beach and then spend a few nights in the Washington DC area visiting with some friends.  Unfortunately, less than a week before I was ready to head down, my DC plans fell through. This radically changed my travel plans and I scrambled to make various plans to make the trip a practical one and one that wouldn’t break my budget. One of the unfortunate facts of being as consultant is that I don’t have an employer that can cover travel expenses. On the other hand, I often have a lot more flexibility in when and how I travel.

I ended up taking the train to Wilmington Delaware and getting a rental car from there. This allowed the most flexibility, was second in time to flying, and overall the least stressful. I love taking the train because I can sleep (which I did on the Albany to NYC segment) and get work done (which I did on the NYC-Wilmington segment, working on a future article for Redgate Simple-Talk and reviewing my talk) Unfortunately, due to a missed turn, some slow traffic due to the rain and then the rain in general, rather than showing up at 5:30 like I had hoped, I was in the door at 6:15 or so. This gave me time for a single chicken wing before I launched into my talk.

I had been monitoring the Meet-up page to see how many people were expected and at my last count it was 8. I was comfortable with that. I was hoping for more, but hey, I’ll take what I can get.  Imagine my surprise when I walked in and there were closer to 20 people there. Honestly, a great turnout! But, between running late, the usual hardware issues of getting my laptop and the monitor talking, and not being able to get one last run through of a 10 minute section of my talk, I’ve got to say I was a bit flustered.

I love to teach. But I would be lying if I said I don’t love it when I see or hear a student have what I call that “Aha moment!” This is that moment when you explain or demonstrate something and you can see the look in their eyes or the tone in their voice when something just clicks. It might be a small thing to you, but for them you’ve just rocked their world.

A number of years ago while teaching the Level 2 cave rescue class in Colorado, we were doing an instructor lead evolution. During these, the instructors take the lead and guide the students through the problem. It’s usually the first real new teaching experience of the week-long class, before that it’s mostly review. In this case I had a single student working with me and we were charged with setting up two lines to be used as a safety and for another purpose.  I told her to grab a single rope and a carabiner. She looked at me questioning because she knew we needed to have two lines rigged. I then showed her the tree I had selected and told her to basically double the rope, tie what’s known as a high strength tie-off using the middle of the rope, clip it in with the carabiner and toss both ends down. Then the aha moment, “wow, I’d never thought of that. That’s worth the price of the class right there.” I’ve got to say I was proud. My job was done, 2nd day of teaching. I could take the week off. Of course I didn’t.

This time around, I was talking about the Model Database and how most DBAs completely ignore it and overlook it. I was demonstrating how when you put objects in it or change various options in it (such as from Simple Logging to Full Logging) any new databases will pick up those objects or options (unless you override the options using a script.)  As I was bending over the keyboard to type the next demo I heard it, someone in the middle of the classroom suddenly said, “Woah…” and you could tell their world had just been expanded. That alone made the entire 36 hours (including travel time, sleeping etc) of the trip worth it. I knew someone had learned something. I live for those moments.

Don’t get me wrong, I enjoy getting paid as a consultant, but honestly, I speak on SQL Server topics and teach cave rescue for those aha moments, for knowing that I’ve just expanded someone else’s world a bit.

Oh that, and in this case, the free wings!

ehb5jp6w4ae8-at.jpg

Tasty wings at Hampton Roads SQL Server User Group

Just a reminder, I will be at the 2019 PASS Summit in Seattle and look forward to meeting with anyone who wants. My Twitter handle is @stridergdm and I often hang out with the folks at MinionWare (they’ve got a comfortable couch) and will be attending the Birds of the Feather luncheon (undecided where I’ll be sitting) and the Women in Technology Luncheon.

And I’m hoping for my nest article on PowerShell for Redgate’s Simple-Talk to be submitted before then!