zhangela

Here are a few articles on why diversity is good for business:

https://techcrunch.com/2018/01/18/diverse-teams-are-still-re...

https://www.inc.com/ian-altman/5-reasons-why-workplace-diver...

Thank you for your thoughtful response!

>>> Measuring diversity based on a few predefined attributes makes no sense. Creating diversity by hiring someone because they're female isn't the answer, we need to go beyond that to truly have diversity.

I think I might have been a tad overdramatic by just saying "I'm not diversity" in the title, but what you wrote above there is exactly what I'm trying to communicate: diversity is more than just bullet points, we need to see it more holistically.

Here are a few articles on why diversity is good for business:

https://techcrunch.com/2018/01/18/diverse-teams-are-still-re...

https://www.inc.com/ian-altman/5-reasons-why-workplace-diver...

Yep I completely agree that gender and race have an influence on our thought process, and perhaps the title of "I'm not diversity" is a tad overdramatic, because I _do_ bring in a unique perspective.

My goal with this post is to convince people to not just limit their views of diversity to race and gender, but also look beyond those 2 to care about the other ways each of us bring in diverse perspectives as well.

Thank you so much for helping clarify! This is exactly what I meant in the article.

Thank you for the feedback!

Agreed the term "extroverted introvert" is not most clear. What I tried to express in this post is "even though social interactions can be draining to me, I'm comfortable being outspoken and actively participating in discussions, which gives me an advantage in the work setting," so most similar to (2) in your description above.

Great strategy! Thank you for sharing.

Agreed it shouldn’t be an even distribution of review requests across the board. That said, if a few people are getting all the reviews, it’s difficult for them to make progress on their project work, and for other engineers to learn code review best practices and get familiar with the codebase.

How do you all make sure the code review requests get load balanced across the team, as opposed to 2-3 people getting all the PR requests?

What does VACUUM, SNAPSHOT TOO OLD, HOT mean?

I still don't know what it is from the website...

this is awesome!