MU Soapbox

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Muxify
    • Mustard
    1. Home
    2. Sparks
    3. Posts
    • Profile
    • Following 10
    • Followers 15
    • Topics 10
    • Posts 976
    • Best 644
    • Controversial 0
    • Groups 4

    Posts made by Sparks

    • RE: Coming Summer 2019

      @BlondeBot said in Coming Summer 2019:

      Everyone is located in a central 'hub' by design and necessity, so people can mingle. And there are infinite adventure plots through planet/crisis-of-the-week events right through that portal that anyone can pick up and play, enough to keep them entertained even if they never touch the meta-plot.

      This was exactly why I had partially built a game (Legends of the Tau'ri)... uh, longer ago than I want to think about, because what spurred me into it was that SG-1 was in its final season.

      The idea was everyone could have several alts among the folks stationed at SGC, and players would be able to run PRPs ('episodes') to other worlds through the gate, taking an SG team off into that plot for a while and then having them return home when done. And staff would oversee a 'seasonal arc' a'la the show, by running 'episodes' specific to the arc, and handing out elements of the seasonal arc to PRP runners to work into their 'episodes'; at the end, you'd have the 'season finale' stuff run by staff, and then a new season would start.

      It was... let's say "heavily influenced by the narrative structure of the show" and leave it at that; with benefit of hindsight, I don't know that it would've worked as well as past-me thought it would.

      And then I realized that a) all of my friends were burnt out on staffing at the time, and b) I was sure as heck not going to run the place alone. So I just shut it down without finishing and mothballed it.

      But I still today love the concept of a Stargate game for the way it so, so easily presents possibilities for a wide variety of PRPs. I'm really looking forward to seeing how this game turns out!

      posted in Adver-tis-ments
      Sparks
      Sparks
    • RE: RL Anger

      @mietze said in RL Anger:

      My son is trans and turns 18 in less than six months. He is out, and I have made comments when they've posted less extreme stuff about "hey, you are talking about my family here" to which they always act shocked and how could I think they hated my kid/my family.

      I am so sorry you and your family are going through this. It's even more aggravating since this mindset—"how could you think I meant that person?"—is so, so prevalent.

      They've actually done studies; people who have gone through life in a privileged/'societal default' (straight, white, cis, etc.) position often see themselves get exceptions in various situations. Someone cuts them slack on a speeding ticket because it's clear they're remorseful, etc.

      These people genuinely get the impression that things work on a case-by-case basis and that laws are wielded only against people who deserve it. And so when someone talks in absolutes about any given group of people—LGBT folks, immigrants, people receiving government aid—they assume they mean all those other ones. You know, the people who are actually being bad by doing that. And because they expect things to happen on a case-by-case basis, they genuinely believe that these broad, sweeping absolute laws they are supporting will be used as a tool, something only taken out when it needs to be used against the nebulous "other/bad" folks in that category.

      "Oh, I don't mean my undocumented immigrant neighbor; he's a responsible father, I love the restaurant he runs, he's a great guy! I mean all those other ones, who are here for criminal reasons!"

      "Oh, I don't mean that person I know who needs financial aid to be able to feed her kids; no, her situation's understandable. We just need to be able to do things about all the people who are cheating the system."

      "Oh, I don't mean that LGBT person who I know. Of course not! They're fine! I mean the other ones out there, the perverts and pedophiles people talk about!"

      This is how you keep getting stories about how Trump supporters are shocked and outraged that their immigrant neighbor who everyone liked got rounded up by ICE. How they're shocked and outraged when their own sister-in-law (or wife!) gets deported. How they're shocked and outraged when someone turns one of those anti-LGBT laws or mindsets against the LGBT person in their family who they of course didn't mean should be included, because they're one of the good ones.

      They're always so surprised when it happens, and upset that this is clearly not what was supposed to happen. Hence the joke around the Internet: "I never thought leopards would eat my face," sobs woman who voted for Leopards-Eating-People's-Faces-Party.

      It's infuriating, because you can't point to the examples they actually know of people in the affected classes; they'll only be offended that you think they mean to include those people. And they'll continue insisting that no one would do it to that person, right up until something terrible actually happens to the person in question.

      It's bad enough when it happens with acquaintances, co-workers, or friends; I'm so sorry you've having to deal with it with family. 😞

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Good TV

      So, I've mentioned before that there are certain books that have opening lines that really stick with you; the one I cite most often is from the Dresden Files books, and is "The building was on fire, and it wasn't my fault."

      One of my other top five favorite opening lines is "Dear you, the body you're wearing used to be mine." It is the opening line of the first book of the Rook Files (called simply "The Rook"), about a woman named Myfanwy Thomas who finds herself with no memory, in an alley, surrounded by a ring of dead bodies, with a note to her from the woman she used to be until only moments earlier. Her life only gets more complicated from there.

      Years ago, a little before the second book ("Stiletto") came out, The Rook was picked up to be turned into a TV series. Season one of that series lands on Starz at the end of this month. And the trailer looks fantastic. I am very much looking forward to it, and I hope it does the book proper justice.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Will it PrP? A place to propose PrP ideas and get feedback

      @Coin said in Will it PrP? A place to propose PrP ideas and get feedback:

      @Sparks said in Will it PrP? A place to propose PrP ideas and get feedback:

      @Coin - based on all past experience with my tabletop group, if I were to think of four possible ways to end a time loop in something I was GM'ing, they would choose the sixth of those four.

      That's why you number them non-sequentially.

      Then their choice would be option i. Wherein 'i' here is the mathematical symbol representing the square root of -1.

      If you do not believe me, you underestimate my players' capacity to throw a wrench in my carefully-laid plans. (I have a lovely little document detailing the campaign's current state I can show you later which might make it clear why I believe this...)

      posted in Mildly Constructive
      Sparks
      Sparks
    • RE: RL Anger

      @Taika said in RL Anger:

      Fuck cancer. That is all.

      I feel you on this so very much right now. My mother is going through chemo, my writing mentor just passed away of pancreatic cancer in April, and an acquaintance has just received a "you have 8 months or so" terminal diagnosis.

      There is, thankfully, one person I know who was diagnosed, but it was early, they removed the mass, and so far they appear to be clean.

      But overall? Fuck cancer.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Will it PrP? A place to propose PrP ideas and get feedback

      @Coin - based on all past experience with my tabletop group, if I were to think of four possible ways to end a time loop in something I was GM'ing, they would choose the sixth of those four.

      posted in Mildly Constructive
      Sparks
      Sparks
    • RE: Real World Peeves, Disgruntlement, and Irks.

      My. Freaking. Ankle. Has. Not. Healed.

      It has been a month and a half. I know severe sprains take a while to heal but I would like to be able to walk around without having to have an ankle brace, and to not worry about sudden stabbing pains when I take a step.

      It is now harshing my mellow and eroding my patience.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @Ganymede said in Accounting for gender imbalances:

      I don't see anything in what Ghost said speaking to your experience or contradicting your frustration. To the contrary, it appears to me that Ghost understands the constant battle being warred in the boardrooms and hiring halls. Yet nothing Ghost has said is, to me, incorrect.

      It is possible to be completely factually accurate in your statement and also display harmful bias at the same time.

      "You should always hire the right person for the job." is a factual statement and very good advice; of course this is what you want to do.

      But take the context; "how do I make this process/workspace more inviting to a new woman who we might be hiring" is often met with that reminder to "always hire the right person for the job", while "how do I make this process/workspace more inviting to the new guy we're looking at hiring" somehow never seems to prompt that same reminder. In both cases, the reminder given is completely correct; the fact that people only feel it necessary to constantly give that reminder in one of those two situations is the thing I think is worth examining more deeply.

      It doesn't have to be active intentional malice or misogyny to exist, nor to be harmful. This example of unconscious bias is something where if you drag it out into the light and look at it, you can see the monster for what it is and slowly begin to kill it. It's not comfortable to do so, but I believe it's absolutely worthwhile.

      Because I can find no reason that almost every mention of hiring a woman needs the reminder to "hire the right person for the job", whereas mention of hiring a man merits it rarely (if ever).

      The advice is perfectly reasonable; the context makes an implication which is not.

      @Ganymede said in Accounting for gender imbalances:

      But you did ask him to step away. And then comes the dogpile.

      I did not ask him to step away, and I apologize if it came across that way to some folks; I was feeling somewhat impassioned and perhaps not at my most eloquent, so I may not have been as clear as I hoped.

      I did ask him to examine his response and posed a question he could ask himself to genuinely self-reflect on if there was an unconscious bias there; it came across as his choice to step away from the conversation rather than do so. That's a valid, albeit depressingly common, choice; no one can really force you into examining your unconscious biases, especially not online.

      But the reason I think it's important to do so is that if you do want to build an inclusive environment, these are exactly the sort of ingrained things we need to address. The unspoken assumption that a woman needs to actively prove she can do the job and wasn't hired just because of her gender identity, while a man is given the time and space to prove he can't do the same job? That's exactly the sort of thing that makes for a low-grade hostile work environment rather than an inclusive one.

      And the sad thing is, at least in STEM fields, most of the women I know just assume they're going to get the former and brace themselves for that low-grade hostility to be their daily reality. It's just the assumed baseline.

      At any rate. It was not my intention to become preachy in a non-constructive manner and it appears I have done so, for which I apologize. (Plus I think I have pretty much expended all the words I have in me to expend on this without just going back and reiterating myself.) So I'll just let what I've said already stand as my statement on the type of things I think we need to deal with—the bits of unconscious bias and assumption we need to drag into the light and kill—if we really do want to make environments inclusive and welcoming.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @Ghost said in Accounting for gender imbalances:

      @Sparks @faraday Just wanna pop in and say that I, in no way, was saying that or had any malice. Politics is just probably the base word to use, but I'm not that guy that groks too much on the whole Convservative vs. Liberal shit.
      [ ... ]
      I said the same thing everyone else did: choose the right people/good team.

      I am totally willing to accept that there was no malicious intent in what you said. But, I really want you to genuinely step back from the situation for a moment and consider what I'm about to say.

      Do you know how many times I've seen a conversation about "So, we have a pretty defined corporate culture, but we need to make some new hires and I'm a little worried it might be jarring or off-putting to a new guy to come into. Anyone have advice on how to make the environment welcoming to him?" get derailed by men stepping in and going "Just be sure you aren't hiring a guy because of political motivations, just to meet a quota!" and thus subtly shifting the conversation to being about whether or not a man was the best qualified for the job? Thus far, in my technical career, that would be 0. (Or nil, or NULL, or None, depending on your preferred programming language.)

      Do you know how many times I have seen "So, I'm a little worried that we're a homogenous corporate culture of guys, and that could be off-putting to any women we hire. Anyone have advice on how to make a more inclusive and welcoming environment at work?" get derailed by a guy stepping in and going, "Make sure you aren't hiring a woman just for politics; if you hire a woman instead of a guy who can do the job better, it will hurt your team!" and thus redirecting the conversation from "how to be welcoming to the women we include" to justifying whether or not women should even be included in the first place? I actually cannot tell you, because I lost count years ago.

      Somehow, the "be sure to choose the right people/team" topic shift only ever comes up when people are discussing how to make a work environment more comfortable for women or minorities. And after a certain point, it doesn't matter whether it's an intentional redirect or acting on an unconscious bias; the effect on the discourse is the same.

      So I ask that you please step back and ask yourself, honestly, if you saw that first question in this post—"what are some good tips I should consider in making a welcoming environment for the new guy we hired?"—would your instinctive gut response to be "Make sure the new guy who you hired wasn't politically motivated; if you hire a man just to have a man, when a woman might be the better candidate, you'll only hurt your team." rather than giving tips on how to make a fun and welcoming work environment?

      If not, then take a minute or so and dwell on that fact.

      Like I said earlier, we—collectively, as a society—need to do better.

      @Arkandel said in Accounting for gender imbalances:

      There are other things we do need to adjust. For example we have two washrooms in our area, both men's... that's gonna have to change unless we expect a new hire to walk across the first floor to use the facilities.

      The guys used to complain about restrooms on the engineering design floor not having enough stalls and how they'd have to wait in line. The first day, years ago, that we had a line in the women's design floor restroom? There was actually a victory email sent out among the women at the company (we made an internal mailing list ages ago) going, "Yes! There's finally enough of us that this happened!" and a fistpump GIF.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @faraday said in Accounting for gender imbalances:

      I'll start by saying that I don't believe that @Ghost's comment "if you take a female candidate who isn't as skilled..." was intended with any malice.

      I don't think in this case it was, no. I suspect it was a thought exercise or playing Devil's Advocate. Doesn't change the fact that it's still something that I'm exhausted by encountering yet again, and for once I wasn't going to hold my tongue on it and play "get along nice". Apparently I had a decade or so of pent-up ire on the topic that needed to be lanced and drained. 😐

      @faraday said in Accounting for gender imbalances:

      There's plenty of research to support the idea that having a more diverse workforce is valuable, so this should be something we strive to change.

      True story of a tangible benefit of diversity: there's a device we worked on at work which is focused on women's health. It was a great project, brought in a lot of revenue, we did superb work on it, the client was thrilled. They gave us permission to publicly talk about the project, and it has helped bring in new clients and revenue.

      I have heard through the grapevine that one of our competitors who also bid on the work was apparently very upset they didn't land that project and we did instead.

      You know why we did? We have women on our engineering team. Enough of them that we were able to staff nearly the entire project with women of varied backgrounds.

      Our competitor did not have the capability to do that and, shockingly, it turns out that having women be the dominant presence in the room working on a device related to women's reproductive health is something the client might actually value.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      No, you know what? Sorry, I'm not actually done. Because apparently I have far more pent-up ire inside me with regards to yet one more instance of something that just happened in this thread than I realized, and—to quote Grog Strongjaw—"I WOULD LIKE TO RAGE!"

      (I shall endeavor my best to keep the post productive, as this is not the Hog Pit. I cannot promise that my tone is not going to be somewhat 'spirited' because—as I said—I would like to rage.)

      Ark started a thread here suggesting that among the candidates for his team, there were women. He said "if one is hired", suggesting that they're going to be hiring on merits, not that they're going to hire one just to have a woman. He wanted to know how to avoid unconscious biases, and how to provide a welcoming workplace without making things awkward or hostile if the hire happens to be a woman. (Because, shockingly, sometimes the best candidate for the job does happen to be a woman.)

      You know what a thread like that does not need? Someone coming in and saying "You should hire the best person for the job. Don't let politics motivate you. If you hire a woman just for politics when there's a man who can do the job better, it will only hurt your team." Which carries the unspoken but extremely strong implication that "the best person for the job" is not going to be one of the women in that stack of resumes, and that if one of those women is chosen it is therefore going to be politically motivated because one of those men could do the same job better. And now suddenly the discussion is shifted from how to make diverse workplaces welcoming to having to defend if the workplace can and should be diverse in the first place; the person has already won, by getting the other group to cede ground.

      It is a technique used almost mind-numbingly frequently to derail topics like this, so much so that it's wearing a groove into the collective social discussion. And I've seen it so often I'm honestly somewhat ashamed I let myself fall into that trap with my last post.

      Now maybe it genuinely is just an idle philosophical exercise to some people to shift discussion of "how" to "if" instead. But to a lot of us in the STEM fields? It is part of our daily professional life in some way or another, not just some abstract thought exercise.

      Please keep that in mind, people, and strive to do better.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @Ghost said in Accounting for gender imbalances:

      @Arkandel I've been in my current IT Ops group for over 7 years now, and here is my advice:

      Build a team who can do the job.

      What you're in is a Catch-22 with your politics. At the end of the day, IT is about skills and experience. It's a Catch-22 because if you take a female candidate who isn't as skilled as another male candidate, your team will suffer.

      Ok, honestly, this was probably not what you meant to come across as, so forgive this minor rant.

      But I'm getting really tired of the implication a lot of people in the tech field throw around that if a woman was hired into a technical role, it's because of 'politics', and that there's a man who could've done the job 'better'. I'm tired of people assuming that 'white dude' is somehow the default, and that any deviation from that needs to be justified.

      I'm tired of women in engineering positions having to work harder than a man in the same role just to prove to guys out there that we actually deserve to be in the positions we were hired for in the first place. I'm lucky that I don't generally have to do this at my actual job; the 'talking over the woman in meetings' does happen, but the folks who do that are genuinely trying to do better, and have asked the women in the company to please call them out when they do it so they can be more self aware.

      But I have dealt with that 'prove yourself worthy of your position' elsewhere. At my current job, I have dealt with it from clients sometimes. I am not the only one, either; every woman in the engineering department has had it happen to them at least once. It's not as bad as it used to be, but that attitude is still out there, and more common than people want it to be.

      There's a fairly stark difference between "I'm hiring based on criteria that are not actually related to suitability for the job because I want to look fair" and "I'd like to ensure I am not unconsciously biased in my hiring, and I'd like to know how I can get more diverse candidates to apply in the first place." I read Ark's question as the latter. Which I firmly believe companies should aspire to. That's not politics, it's just good sense.

      Because there is demonstrable value in diversity. There are studies about this, and I have observed it firsthand at work. If you have a team of all straight white dudes put into a conference room for an engineering brainstorming session? A group of people with generally similar viewpoints will consistently produce a smaller variety of ideas, because... well, they have generally similar viewpoints. Once you start introducing people of different backgrounds—people who, due to those backgrounds, often look at the same thing in different ways—a brainstorming session produces a wider and more varied set of ideas and approaches.

      Similarly, a diverse engineering team means problems that arise during actual development of the particular device we're working on can be approached from several different angles, and we often find solutions in a diverse group that a homogenous one blows past.

      The benefits diversity brings to our various engineering projects have been genuinely observable in ways we can measure; the reason the company wants a more diverse workforce is not politics, it's because we get more shit done and make more money because our clients are happier with our work than our competitors.

      This doesn't mean you should go "Oh, here's a candidate that's a woman, we should hire her." or "We absolutely have to make certain our engineering department looks like a Benetton advertisement." But it does mean you should work on dealing with unconscious bias. And it does mean you should work on attracting more diverse candidates to apply in the first place, so that the pipeline offers more diverse options anyway.

      Because, frankly, if someone thinks that hiring a woman means it was 'your politics' that forced it, because 'a man could do the job better'? The implication that the hiring decision even has to be justified as not politically motivated when hiring a woman, whereas it doesn't when hiring a man? That attitude's politically motivated, too. And those ones are shitty politics.

      (ETA: Okay, turns out that was not a "minor" rant.)

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @Tehom said in Accounting for gender imbalances:

      @Sparks said in Accounting for gender imbalances:

      Putting on my "hi I have hiring responsibilities" hat, I can say that while a sizable gap in work history would earn a raised eyebrow from me, that's easily made up for—at least to me—if you have side projects out there you can point to. Especially side-projects that are open source and on Github. I love those! Please include things on Github in your resume! Then I can see your coding style! I can see if your commits are nicely separated into bite-size updates or if you have giant commits touching the entire code tree at once encompassing like two weeks of work! (Why do people do this?? That's not how source control is supposed to work! It wasn't how it was supposed to work even before git's distributed model!)

      I feel so called out right now for --squashing my commits.

      j'accuse

      Seriously, it is actually considered very bad practice at my workplace. Leaving commits in smaller chunks makes it /way/ easier to figure out which change exactly broke a build or introduced some kind of instability, and to roll just that change back. It's really important on firmware projects.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @faraday said in Accounting for gender imbalances:

      Side tangent. I think that's just a matter of being used to one vs the other. I think that Python is a perfectly fine language as well, but as someone who learned Ruby first, there's just a cognitive dissonance because things are similar enough to feel like: "Oh! I know this!" But different enough to be like: "Crap, that totally doesn't work."

      Oh, definitely that. It's whatever you used first, or whatever you use most often. I'm getting a little rusty in Java, even though I've known it longer, because everything I would've done in Java for Android test harnesses and such I'm now doing in Kotlin. I've been toying with Ares on the side, experimenting with adding some features, and even just doing that has been exercising the metaphorical muscle memory (i.e., the "oh, right, I can do this that way in Ruby" knowledge); now switching between the two feels like the difference between driving my car and my housemate's car, versus driving my car and a random rental car. 🙂

      Which—back on topic!—is why I do like to find out when interviewing someone what the language they're most comfortable in is. Like, if you are interviewing for the team that's responsible for cloud/enterprise components of an ecosystem? If you write all your stuff in Ruby these days, it would be somewhat cruel of me to then test you in Java, even if you know both; I want to see how you work through the problem presented, not watch you stumble with "oops, the gear shift is on the center console here rather than a stick on the steering column" as you try to adjust to a different language.

      (If you answer that your preferred language is PHP, though, that should honestly be grounds for instant disqualification.)

      @PuppyBreath said in Accounting for gender imbalances:

      As a woman who excelled in a coding bootcamp and received a 4.0 while finishing a degree in Software Dev, I've largely given up trying to find a job in tech because I'm the worst interviewee and generally terrified of men.

      I feel you on the nervous interview thing. I think six years of being in a hybrid engineering/management position where I actually have to review resumes and do interviews—as well as being in a client-facing role where I have to talk to clients—has done wonders for letting me feel more in-control and collected when in a meeting or interview where I might otherwise feel nervous, but that really just sort of allows me to hit 'snooze' on the nervousness.

      (Which means I will then leave said situation, go somewhere private, and go "WAAAAUGH" as the snooze button runs out and the nervousness hits at once.)

      @PuppyBreath said in Accounting for gender imbalances:

      I'm not sure why I decided to get a degree in a field dominated by them. Add in my now sizable gap in work history, and I'm basically unhireable despite not sucking at the actual programming stuff.

      Putting on my "hi I have hiring responsibilities" hat, I can say that while a sizable gap in work history would earn a raised eyebrow from me, that's easily made up for—at least to me—if you have side projects out there you can point to. Especially side-projects that are open source and on Github. I love those! Please include things on Github in your resume! Then I can see your coding style! I can see if your commits are nicely separated into bite-size updates or if you have giant commits touching the entire code tree at once encompassing like two weeks of work! (Why do people do this?? That's not how source control is supposed to work! It wasn't how it was supposed to work even before git's distributed model!)

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @Kanye-Qwest said in Accounting for gender imbalances:

      @Sparks yeah it's not great at my company either, but we have teams of people working on it, on recruiting undergrads and partnering with STEM facilitation community programs for the future, which I love. We had a Black Girls Code workshop here recently.

      I think it's going to be better going forward. We're much nearer parity with our paid interns lately, especially in electrical engineering.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @Kanye-Qwest said in Accounting for gender imbalances:

      But also..what is wrong with your company, that you've never had a woman on this team, ever? Maybe you should hire all the women. Start making a dent in that problem.

      I admit I'm lucky; in my company, one of the three DoE (director of engineering; one for software, one for electrical, one for mechanical) roles is filled by a woman. Two program leads (the people who report directly to their DoE and keep that engineering discipline running smoothly, and mentor other engineers) are women. About 10 of the engineers, across all disciplines, are women, as are more than half of the project managers. (And, as is true at many companies, most of the HR and finance departments.)

      But it's still like... maybe 28 women, total, in the Seattle office? Out of around 110 people? It's way better than a lot of places I've worked, yes, but that's still only around 26%.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @Auspice said in Accounting for gender imbalances:

      @Sparks said in Accounting for gender imbalances:

      @Auspice said in Accounting for gender imbalances:

      My father is a developer. Apparently he used to, if he saw a job he was interested in but didn't know the language, put it on his resume, apply, then go out and buy a couple books to teach it to himself leading up to any potential interview.

      So, so many guys do this. So many.

      I mean, he managed to pull it off but it baffles me to this day. I can't learn shit like that. I'm over here trying to switch gears from learning python to ruby and I wanna cry sometimes. XD

      whispers into your soul Python is better. Stay with the Python...

      In fairness, Ruby's actually a perfectly fine language and well worth learning. I'm personally just used to using Python on a daily basis to create CI build scripts at work, for machine learning stuff (which is primarily in Python these days, it feels like), and so on. After so much Python, doing Ruby always feels like I'm driving someone else's car for a bit; I know how to do everything, but the windshield wiper toggle is in the wrong place, the parking brake is a pedal versus a stick, etc. So I just have to force my mind into Ruby mode instead of thinking Pythonically, and that annoys me enough that I default to Python for things.

      (That said, I wish that they'd gotten the Ruby-style safe navigation operators into Python prior to the not-yet-released 3.8 version; i.e., Python's upcoming ?. equivalent to Ruby's &. operator. C'mon, guys. This thing is sanity-preserving, and should've been in Python 3 from the start.)

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @Auspice said in Accounting for gender imbalances:

      My father is a developer. Apparently he used to, if he saw a job he was interested in but didn't know the language, put it on his resume, apply, then go out and buy a couple books to teach it to himself leading up to any potential interview.

      So, so many guys do this. So many.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      @Caryatid said in Accounting for gender imbalances:

      A better way to show instead of tell (thereby risking her reading into a well-intentioned question that still gives weird vibes) is to, before or after the interview, tour the interviewee through the workspace.

      This. When we interview people, they will have three interviews: a phone screen, a technical interview, and a social interview. The phone screen is obvious enough. When they come in for the technical interview, they'll be scheduled for a social interview too. In the social interview, you get 3 or 4 randomly-picked folks at the company who'll sit down and just get to know you. What's your sense of humor, etc. Basically, are you a cultural fit? And in return, the interviewee gets to ask any questions they might have about the company culture. (We also give them an office tour, separately from the social interview.)

      I think that is a huge deal. One of our most recent hires (she's a freaking rockstar programmer and we were so lucky to land her) was considering which of two jobs to take, and the social interview at our company is why she went with us. She found out there was a D&D campaign run at the company, that there's a book club for SF/fantasy books, etc., and went "My people! I shall join them."

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • RE: Accounting for gender imbalances

      So, I get to do software team interviews and resume reviews, and I'll tell you the things I've noticed (and which I've realized I'm prone to as well on the other side of the divide):

      • Women in tech will often downplay our own achievements and skills. This means that a woman's resume will often (but not always!) leave out anything that isn't one of the most notable bullet points, will tend to omit skills in the 'skill list' that aren't at really expert levels, etc. Conversely, a lot (but not all!) of the resumes I've dealt with for male engineers will have any skill they've ever used in the skills list. "I know C++" does not always mean what I would read it to mean; I've encountered folks where it means that they've written lots of C code, glanced at some C++ source on github, and thought "okay, classes! I know those from Java. How hard can it be?" (And then they get into the STL and start to weep tears of blood. ANYWAY.)
      • Women are not (usually) as good at—or at least as prone to—bullshitting. I've met guys who can talk their way through an interview sounding like they know everything, then hit the engineering floor and start flailing. I see this most often with wireless tech; more than once, I've had a guy cheerily tell me how they're just great with Bluetooth Low Energy, and I'm like "Cool! Can you show me how you'd design a simple protocol to do <X> over BLE?" and things come to a screeching halt. I have not had that with a woman in interviews.

      The practical upshot of this is that given a man and a woman of exactly equal skill level applying for the job, the man will very often look 'better' on paper and talk a better game in an interview. I just have to keep this in mind when reviewing resumes in general, and then do actual technical interviews.

      Note, I do not like 'program this solution' tests for technical interviews; I know I can't always write actual code on a whiteboard under pressure, and I'm the freaking Program Lead. So I test technical skills in other ways. Like:

      • You say you've got great experience in wireless communications? Given this use case, sketch out the basics of a protocol that will get the necessary data transferred over Bluetooth 4.1 without any major inefficiencies, which will be easily processed on resource-constrained silicon, and do so without using so many characteristics that it would break Nordic's Bluetooth radio firmware.
      • You're an expert debugger? Awesome! I have what I call the 'train wreck' file; really horrible bugs which are not at all obvious on first glance. Let's grab one in a language you know, let's say that given this particular bug-induced behavior, if you'd narrowed the issue down to this piece of code, how would you go about fixing it?
      • You're really familiar with low level silicon on ARM chips? Sweet! Let's talk register access on a Cortex-M3; what happens if you create a register variable and do this? Or let's go over the implications and uses of the volatile keyword!

      Things like that. I come up with technical challenges that let me see their thought process, rather than their "woo, I can write a program to efficiently calculate an integral image on the whiteboard". I find that this works really well to show me who's bullshitting (or who would've read up on glassdoor to get our usual programming questions and memorize a solution) versus who can actually take a design or debugging problem and work through it. People who know what they're doing will have a lot more confidence when questioned in that way, rather than being put on the spot with "Write a C++ program to efficiently calculate an integral image on the whiteboard."

      I would also definitely concur with the "do not make your first woman hired about 'Look! We've got a woman on the team now!'" You do not want your new hire to feel like they were hired to meet a quota, much less to feel like a zoo exhibit.

      posted in Tastes Less Game'y
      Sparks
      Sparks
    • 1
    • 2
    • 7
    • 8
    • 9
    • 10
    • 11
    • 48
    • 49
    • 9 / 49