Women in IT

J stands for Joanna.
In Polish there is this rule that female names must end with vowel. I'm a .NET developer with, nicely said, 10+ years of experience. I read a lot about all those diversity problem, programs like 'woman to Polytechnics'. This is now a day a real thing. There is not enough developers and employers are looking for people to fill the gap, I really understand it.

But on the other hand all this fuss, all those articles (some of them good, some totally not worth spending time on reading), all those actions, imho, are making noting good.
The most prominent change I see in official Microsoft events. Visual Studio 2017 premier event was fully differentiated - women, Americans, older men (age discrimination is also a thing) and Scott in two persons ;) This was great! aanndd it wasn't. It felt so forced and artificial. This is only a wind of change and it will take time to feel natural. It will take a lot more time in Poland, in my opinion. 

In Polish there is this "joke" 'kobieta programistka jest jak swinka morska. ani swinka ani morska' in translation it isn't as good 'woman developer is like Guinea pig. neither pig nor Guinea'. After hearing this joke hundred times I started to ignore it but it still sometimes hearts my fillings on bad days. 
But wait can developer have feelings? There is a little problem that women - don't have nothing box and small jokes just accumulate. The next problem is that women should not curse, be unpleasant or rude. Being cynical is a behavior that doesn't suit a woman. 

I had an interview today. I've asked how looks the team that I would join. The answer was 'well there are three men' and a little giggle. I don't even know if there is a tester on this team.
The answer was one of those little things / innocent whips that adds up into decision 'I have had enough! I'm leaving'. I had already tree times when I wanted to change a profession. I've solved it with a lot of love for developing and a lot of unemployed time spend on bike or any other activity that didn't involved working computer.    

There is a lot more. I could make a story on each of those: The ‘manterruption’, The Real Reason Women Quit Tech, The ‘Women in Tech’ movement is full of victim blaming bullshit, The Rise of the 'Brogrammer'. Each of them addresses one or many problems that I've meet on my path. I don't want to talk about all of them. I don't even want to make a point. And I know that I'm not the only one with all those problems. But most women don't talk about it. Endure or change career. 

Well maybe I wan't to make a point. There is a problem. There are many problems.
And additional problem in Poland is that no one knows there is a problem.

Cynicism is an unpleasant way of saying the truth. 

Comments

Post a Comment

Popular posts from this blog

Azure post deployment scripts

Image
Let's do a trick. After deploying application (that was easy with Ftp or Git ) it would be nice to take some action. For example send an email, or write release notes to release page. I will do much fancier thing - I will write some text to console output.
Read more

Mobile view lifecycle. Fixing Xamarin.Forms Page lifecycle

Image
For mobile applications the highest priority is user. What user can see and interacts with. Application should react not only on user interacting with it but also user interacting with operating system. That's why not only application has it's own lifecycle but also "view" has it's own lifecycle. In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is being suspended and reactivated. View know quite a lot about outside world and view lifecycle is very similar to application lifecycle. Compare below first application and then view lifecycle diagrams: In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is
Read more

Mobile application life-cycle Android vs iOS vs Xamarin.Forms

Image
Lifecycle. One of the most common recruitment questions. No matter what technology you work with this is something that should be well known and understood. It's good to know how application behaves, what it is allowed depending on its state and when to react on specific lifecycle events. In mobile world lifecycle is even more complicated because there is no 1 answer but 3 in this case: Android. iOS. Xamarin.Forms. I use also Xamarin.iOS event names in my diagrams, but the sequence is the same. Lifecycle is the definition when your application have access to resources and when react on state change. For mobile the biggest priority is what user can see and interacts with, so active application have priority in using system resources. System has limited pool of resources, so  applications running in background (not visible to user) is limited by system in how much resources can it use and also system decides when application needs to release all resources (be closed/killed/end o
Read more