| This article is hilariously bad. The argument goes: I like CSS more than Tailwind
-> Why don't people like CSS more?
-> Maybe because 'CSS, which makes things look ‘pretty’, is considered feminine' You're entitled to like CSS more, and I could even agree making things look pretty is feminine coded, but it obviously doesn't explain people's preference for Tailwind because Tailwind also exists to make things look pretty. --- I've worked with plenty of female engineering leaders, and most of them have a backend background. The reason for this imbalance has nothing to do with gender, but entirely to do with criticality. Given that frontends tend to read/write from the backend, the domain model is usually owned by the backend in most apps, meaning that capability design and expansion is gated by the backend. Not to mention that screwing up your backend architecture is in 95% of cases a much much deeper problem than screwing up your frontend. A data migration is basically always harder than redesigning the UI for some app. |
As to your other views, I think you have several errors. The biggest is declaring "it has nothing to do with gender" in a very gendered society, one with a long history of bias, and thinking having one (weak) alternative explanation is sufficient to explain executive hiring patterns.