What about women?

I think the reading was amazing, specially for the month we are in. It is very interesting to know the article mentions all these prominent women in Computer Science who did not get in their time the recognition they deserved. On the other hand, I knew before a lot of the facts about women in computing the article mentions. I can recall that my sister once explained to me that the first programmer was a women because men were most suited for hard labor such as Electronic Engineering and not for something soft as software.But then, just as the article mentions it, the things changed and the number of women in the area drop suddenly because they were replaced by men who saw potential in the area.
In this specific area, discrimination against women began due to the high payment job that it represented and also because it was a nerd job, a job for people who often have trouble talking with anyone, people that is really mean. And, if you add up all of these with the fact that women were considered inferior the past century, it all adds up for the segregation of women in the area. Today, we still have that segregation and a lot of women quit their career in Computer Science due to the stigmas around being a coding woman.
The last part of the reading focuses on how to address the gender difference in Computer Science. Nowadays a lot of schools are trying to close the gender gap in STEM careers and, even though it is difficult, I think that articles like this one can help to close the gap.  I also found pretty cool the study about creative and artistic women pursuing a degree in Computer Science, but I think that with movements like Codess and other women empowering proposals we could have more women in the area to work side by side in what I consider one of the most awesome career choices.

Comentarios

Publicar un comentario

Entradas más populares de este blog

Two is more than double of one

This week's reading talks about pair programming, a software development practice in which two developers work at the same time in the same project in the same thing in order to keep track of the work in case one misses. But it also improves times, productivity and software quality. The reading's goal is to facilitate the transition to pair programming by explaining how you already know how to do it. The text begins explaining how pair programming in the XP methodology for development is really successful and how programmers attribute the success of their productivity and the methodology to the technique. And although many programmers tend to work alone and resit to the change, most of them  succeed in the transition to pair programming and begin loving it. The first rule of pair programming is Share everything, even mistakes. The second one is play fair, meaning that you shall not take the control of the development and let the other person also be the one who codes. The thi
Leer más

What makes Lisp Lisp?

I found this last text repetitive and boring, I think I had understood where Lisp came from and almost everything there was to know about its story in the previous readings and podcasts. The only part of the reading I found interesting was the eval definition function where they showed you how to write the Lisp interpreter in Lisp. The thing with programming using a functional language is that is a complete flip of paradigm, when the data is also the code and you need to differentiate it using quotes. One of the difference I found in this reading regarding Lisp and Clojure is that in Lisp the empty list represents false and the atom t represents true where as in Clojure we have true to represent true and false or nil to represent false. Also, I noted the differences between the primitive functions in Clojure and in Lisp, where in Lisp they are called weird and in Clojure they have the name of what they do. This last I noted since the podcast about Lisp that explained why the functio
Leer más

Is really functional programming better?

Since the beginning of software development, we have used the same programing techniques, the author mentions that this is because it “closely resembles how a computer works at the hardware level: the processor fetches data from memory, performs elementary opera- tions on it, and writes the result back to a memory cell” (Hinsen, 2009). The only different technique that has been developed is functional programming, which was developed as a mathematical theory first and then into a programming language called LISP. So, we have two different approaches: functional programming and imperative programming.   Functional programming consists on composing functions for computations, just as previously mentioned, this paradigm was first a mathematical theory and thus a function is “a mapping from input values to output values” (Hinsen, 2009) not to be confused with subroutines. A big difference between functions from functional programming and from imperative programming is that functional fu
Leer más