|
|
|
|
|
by zdragnar
2852 days ago
|
|
My point was that, without knowing the management's perspective, it's entirely possible that gender was merely a coincidence of having senior males available, and hiring junior females either because they were the best available or the company wanted to look diverse. Perhaps they were flagging and needed to cut the junior developers so the senior developers could focus on getting back on track. Either way, it's impossible to know, because without more details all we are left with is the agenda of an author who isn't interested in presenting the truth (or providing sufficient evidence to support it). Edit: consider the following scenario: you have a team of male developerd; maybe they were friends when they pitched the idea for a product to you. After a few months, there's a big backlog, and they want to hire junior developers to train and take off some of the pressure. To embrace diversity, you hire a bunch of women who recently graduated from a boot camp to round out your all white male staff. Fast forward a year. Everyone has become a tight knit team, but the pressure to deliver mounts. Instead of getting faster, they're all bogged down with refactors and endless pull request revisions of things that aren't working out. You are running out of money, so you decide to cut the junior developers, and try to bribe the senior devs with some of the cost savings to make up for all the extra hours they'll now be working. Uh oh! You're only firing the women! They all band together, oblivious to the fact that you literally won't be able to keep them all on. I'm not saying this is what happened. What happened could have been pure sexism and anti-labor mentality. BUT pushing such an agenda without KNOWING that is the case here doesn't do anyone any favors. |
|