22 karma · joined September 20, 2022
I'm now working at a smaller firm and get to be a major influencer and decision maker in how the culture is getting laid out. It's mind boggling how much trauma/PTSD people bring to the table from working in offices that are really homogenized and lack diversity with them being the one that's different. I still can't get over how common it is regardless if it's gender, sexuality, education background, or disability. What I think a lot of people are missing in the DEI discussions isn't about trying to find diverse candidates but how to create environments where they - along with everyone else - thrives.
It's pretty obvious from the comments in this post how there's a strong vocal minority of people that refuse to engage and constantly battle how broken things are. I just hope they figure it out before it's too late. And if they refuse, I hope they remain ICs with very little influence and not included in significant decision making because this attitude is poison for so many people.
When it comes to a recruiting pipeline this is critical. If you are tapping members of your team to help finding candidates from their networks and your team lacks diversity, you are going to just build out your team with more of the same.
The same goes for where you are looking for candidates outside of your team. If you are only targeting a small number of schools it's really easy to end up with a homogenized set to pull from. I know from experience working at some of the big tech powerhouses, they'd target a handful of schools and only hire college grads from there - which means they miss out on recruiting from state schools, historically black colleges, and other pockets where things are more diverse.
Also, what are "bizarre sexual proclivities"? It sounds like you are living with a thick layer of judgement and shame in your life. That sounds rough.
That's a really interesting way to slice and dice it. When I read your first few sentences that's not how I interpreted it at all.
I got fact, fact, optimist. Optimist, fact. Fact, optimist, optimist.
But I'm not convinced that's a better way to go about it. What is likely needed is each of those chunks to be taken into context and when I look it at that, it's really "here is a problem and a solution to move things forward." To me that's optimistic. If it were pessimistic, I'd expect it to be "here is a problem and there's nothing we can do about it."
How has the Postgres DB worked out for you with Render? I've been weary of using a relational DB in general since it's a single point of failure and really disruptive if your instance goes down (even with a back-up DB to failover too can be problematic if data doesn't get replicated before a crash).
Also are you just using your Node.js app as a back-end server or are you also serving web pages from it?
As for keeping the number of accounts down, I've seen that blow up significantly if you have someone break into an account or have a disgruntled employee that can get into a single account and wreak massive damage. Or if your software runs in multiple regions and you need to meet compliance requirements like GDPR, etc.
This can really help manage complexity but it the more this account grows the riskier it becomes if a bad actor breaks into the account (ranging from fraudsters/hackers to disgruntled employees).
I don't necessarily blame anyone for falling into these categories. Sure there are annoying egos and some people can be overly confident when it's unwarranted. But it can be very difficult for people to figure out where they fit, especially when they don't know what they don't know.