This is a pretty sad thing to see in something purporting to be journalism. I can't blame the really writer though. They probably only had 30 minutes to get something out the door to drive their view count...
Sure the journalist could do that search for every university - but why would she start with MIT? She (Sarah McBride from Reuters, not a click-bait agency) also talked to UCLA and Harvey Mudd, both Californian schools and on her beat (as a SF-based journalist). Harvey Mudd had a reputation for high female enrolment in STEM and was a more logical first call than MIT, on the other coast.
The article tries to present Stanford as relatively unique in this light — which is great for Stanford but potentially bad for the overall ecosystem. It shores that up with the vacuous statement about how it is "unclear if Stanford is the only major U.S. university [...]".
A few minutes of online research (or perhaps an hour(s) of calls to registrars) would have resolved that. Then she could have made a concrete informative statement like "[?All] of the top 10 ranked schools (via US News and World Report) have seen a significant increase in female computer science majors." and/or "MIT & [...] also reported that CS is the most popular major for women."
This is cool, and interesting in a couple of ways. The declarations are preliminary, meaning (I presume) that students may change their minds; according to some studies (e.g. [1]), women tend to transfer out of CS at a higher rate than men. Some anecdotal reasons behind this include a hostile atmosphere/alienation [2], sexism from students and teachers, unequal backgrounds due to pre-college factors [3] and so on (of course, there are plenty of non-gender related reasons why someone might switch majors).
The flip side is, these are upperclassmen, which I understand to mean they probably have been taking CS classes for some time already at Stanford. Most of these factors would have been encountered already if they are indeed present at all, which is cheering in its own way.
I wonder how much of the underrepresentation of women in this field is due to it being low prestige relative to other formerly male-dominated fields such as medicine or law into which women have made substantial inroads, because women seem much less willing to enter male dominated fields, however well-paying, if they lack prestige (electricians would be an example).
If I'm correct, then the very same media outlets lamenting the lack of women in CS are actually partly to blame for it for their ongoing denigration and belittling of those already in the field. For example, someone in this thread cited an NPR article titled "When Women Stopped Coding." Does "coding" sound like a prestigious job activity to you? How many news articles have you seen lately that casually refer to psychiatrists or psychologists as "shrinks," and how many have you seen that refer to us as "coders," "geeks," or "nerds?"
As a physician, I don't think any of us have the perception that programming is lower status. Our in-jokes are usually about how we can't find housing on our salaries because the former computer science majors are driving up the prices.
"Does the staggering wealth of particular engineers and programmers mean that there is any chance for nerds to rise socially?
Stammbach worked with a colony of longtailed macaques. In the paper cited above, the running header is "Responses to Specially Skilled Java Monkeys." Stammbach took the lowest-ranking macaque out of the society and taught him to operate a complex machine and obtain food. When the nerd monkey was reintroduced to the society, the higher ranking macaques stopped kicking him out of the way long enough for him to complete operation of the machine and obtain food for the community. I.e., society cooperated to create the conditions under which the nerd could toil for them. However, the monkey who acquired these special skills and provided for the society did not achieve any rise in his dominance status."
Phil Greenspun's title for the above was "Java Monkeys."
(I personally don't have an opinion about the status of programmers relative to other professionals and how it affects women, so just commenting on your remark.)
as someone who works around hundreds of MDs daily. I would say they all look down at CS degrees, in fact at my work, a masters in CS still gets you the label of "unskilled labor" but a CNA with 6 months of training is not.
Where have you seen Media outlets talking about Programmers are "geeks" or "nerds"? I recall The Register calling scientists "boffins" but not using the other two words for Coders.
I have absolutely no problem with "Coder". At the risk of sounding grand and dandy, I think people realize the impact Code has on their lives, and being called a coder makes me very happy.
I agree with your apprehension over Geek & Nerd, though, it's a badge of honor for you and me but maybe not within wider society. But still, which media outlets?
Oh BTW: Interesting point about "prestige" affecting womens' choices in profession. I did not give that angle much thought, I'll talk to some of my female colleagues to verify.
Being called a "coder" implies you're performing mechanistic grunt work of manipulating symbols with little thought to architecture, or really without any implied discipline. It's akin to identifying a writer or journalist as a "typist". Though I suppose that's what many "coders" do, go figure.
The media by and large does not care about programmers, only insofar as there is overlap with Internet entrepreneurs.
I agree with you. It's all highly subjective, of course, but my own perception is there's a slightly negative connotation to calling someone a "coder." If you don't think so, you can at least agree that it's less positive relative to "doctor"/"lawyer"/"manager." Heck, even "designer" has a slightly fashionable connotation to it.
Perhaps it's not prestige so much as risk-aversion. Programming is a very cyclical industry (akin to oil or construction), whereas there's always a need for doctors and to a lesser extent lawyers.
Edit: Certainty this isn't the only reason to choose another career besides software, I just thought I'd respond to prestige as a particular reason.
Woz, Bill and Larry were coders, geeks and nerds at some point, and in many ways still are. Are they prestigious? I guess it's up for the reader to decide.
They're famous and respected as businessmen and philanthropists, not software engineers. The media and general public are largely ignorant of the technical accomplishments of those men and would pay them little notice had they not been so phenomenally successful in business. Compare the responses to the deaths of Steve Jobs and Dennis Ritchie.
Well sure but nobody cares about most Nobel prize winners either, and nobody cares about great poets. It's just that money is an "objective" yardstick, you either have it or you don't, which makes it easy for people to wrap their head around.
However, I would argue that if he wasn't a foil to jobs he wouldnt be nearly as interesting, there are plenty of equally/more deserving engineering geniuses in the world, no matter how gifted woz is.
I don't quite understand if "Majoring" means completed degrees or not.
In my old University, women were common in the first year of Comp Sci, as it was the easiest department to gain entry to for them as females because of quotas or whatever positive discrimination is called.
However in the second year, they would typically transfer out to another department they were more keen on, but probably wouldn't have won a place at initially.
Anecdotally, it seemed like all of the ladies in my CS department wound up actually majoring in Cognitive Science, which was part of the CS department technically, but about half psyche and pre-med, really.
I think discodave is asking for evidence that quotas are in use for these courses, as oppposed to evidence that quotas increase numbers of otherwise-underrepresented groups
not the parent, but the discussion is of interest for me. I've quickly run a search query for "affirmative action statistics for computer science". First page result included a report from http://www.civilrights.org/. I am ignorant of veracity or validity of this organization, so I can't verify if its contents are sufficient to be "evidence". But here goes(emphasis mine):
"By 2010, one in four new jobs will be “technically-oriented,” or involving computers. However, women still lag far behind in earning computer technology degrees and working in computer technology-related professions. High school girls represent only 17 percent of computer science AP test takers and college-educated women earn only 27 percent of bachelor’s degrees in computer science (down from 37 percent in 1984) and 16.3 percent of doctorate degrees in computer science. Overall, women comprise roughly 20 percent of IT professionals. (“Tech Savvy: Educating Girls in the New Computer Age,” American Association for University Women, 2000)" [1]
Barring the "down from 37 percent" part, it tells me that 17% of female high schoolers take AP computer science, but actually a higher percentage of women end up with a CS diploma. It's very thin connection but that does raise a question that affirmative action lets in more women.
Stanford doesn't separate undergrad admissions by department. When I applied, the application didn't even ask what my intended major was. All Stanford undergrads start out as "undeclared", and many don't choose a major until sophomore year.
Ok, so women still choose CS at a smaller proportion than men do...that's alright for now.
What's awesome is that women are now choosing CS more than any other major, and Stanford is providing them an environment where it's cool to do so. That's incredible.
In all fairness, this is likely a structural data anomaly. ie, it is driven by the number of majors at the school, and their level of abstraction. Here are some historical data points.
Notice the arbitary abstraction of, eg
Bio Sciences
Human Biology
1955
1. History
2. Economics
3. Psychology
4. Political Science
5. Bio Sciences
1965
1. History
2. Political Science
3. English
4. Psychology
5. Economics
1975
1. Psychology
2. Bio Sciences
3. Economics
4. History
5. English
1985
1. Economics
2. Human Biology
3. Bio Sciences
4. Electrical Engr
5. English
1995
1. Bio Sciences
2. Human Biology
3. Economics
4. Psychology
5. English
and now we look at 2010 (from quora)
Biological Sciences (1.32%) but
Human Biology (12.58%)
Biology (5.74%)
=~20% of Standford majors in 2010 are "biology majors" in plain language usage.
Based on data on Bachelor's Degrees conferred in the 2009-2010 school year[1], the top majors are:
Human Biology (12.58%)
Economics (8.10%)
International Relations (6.20%)
Biology (5.74%)
Computer Science (4.94%)
Engineering (4.71%)
Psychology (4.54%)
Political Science (4.25%)
English (3.96%)
History (3.62%)
Management Science and Engineering (3.39%)
Mechanical Engineering (3.10%)
Science, Technology, and Society (2.30%)
Communication (2.18%)
Electrical Engineering (2.07%)
Mathematics (2.01%)
Earth Systems (1.84%)
Physics (1.84%)
Sociology (1.49%)
Biological Sciences (1.32%)*
I suspect that differentiation would make more sense if they replaced "human biology" with "pre-med".
I graduated from UVA In '99 and the biggest majors by far were psychology, sociology, history and economics, possibly in that order, but definitely each having ~500 graduates (out of a class of perhaps 2800-3000). I think the entire engineering school only graduated about 300-400 people each year (at that time).
Is that really awesome, or is is bad news for say engineering or physics which could be losing those same women and are traditionally even more male dominated than computer science is? If those subjects are losing as many women, then this is actually bad news for gender same-number-ness.
There's been a significant change (at least from my perspective) in the awareness of inequitable treatment of women in tech in the last few years, and I'd like to think that's one of the contributing factors to this change.
If true, that means that the previous levels of entry into other subjects were (in part) due to students rejection of CS. If CS loses its repulsion factor then that brings everyone's metrics back to neutral and will make other problems clearer.
Much as I hate to wheel out the trite "everything is a market" trope, the more subjects like physics will have to work to improve the treatment of women in science (although my perception is that it's not as bad as tech)... and maybe (one day) the way science is run to make it a more appealing career.
I was a physics undergrad and chose to ditch science as a career at my first opportunity. A majority of the people who stayed on to do an MSc or PhD did so only because it would buy them a well payed role at a bank, or PWC, or Anderson (sorry, "Accenture"). It's a shitty career, fighting for funding or tenure, full of victorian-era bullshit.
The sooner physics (for one) cleans house the better.
I don't think this is really a case of Simpson's paradox.
What we're seeing is that female students at Stanford are less concentrated on a single major than the male ones. As a result, their top pick isn't as high as the male top pick. I'd guess that the distribution of female majors is higher entropy than the male one.
Simpson's paradox would be if there was some second confounding variable that corelated to gender which was causing these results. There might be, but I'm not seeing it.
> Because men haven't found gender related hostility or exclusion from high paying jobs in those majors.
Men do face discrimination in nursing. However, men are still paid more on average than female nurses[1]. Make of that what you will. The thing I find most striking is that before the 20th century, most nurses were men and in the early days of computing there was a much higher number of women in the field.
Generally, when we use the term "gender gap" in this context, it refers specifically to a wage gap and not other gaps. Sorry for not making that clear.
"computing" was a secretaries job. It was a position typically filled by a woman who worked with numerical data (working with spreadsheets, calculating an insurance premium, etc...mission critical back end stuff). During WW2 pretty much all these jobs were filled by women.
Computing and IT started to come of age during the post WW2 boom so there would have been a lot of women with the math background to make programming and working with computers somewhat of a logical next step in ones career.
Coincidentally, these woman who had math backgrounds were also some of the fist to have their jobs automated out of existence (the woman who calculates someone's insurance premium is replaced with a box of punch cards).
Just speculating but it wouldn't be a stretch to see how when choosing between going home or switching careers the woman who didn't become the stereotypical 50s-60s housewives as their jobs were automated found new jobs writing punch cards (programming) and operating computers.
(i'm in a hurry, probably lots of grammar mistakes in that)
Correct, that was the case with a number of the roles. Those roles were sort of like the modern day CRUD development and things that (mostly) get automated away.
However, Grace Hopper[1], Betty Holberton[2], Frances Spence[3], along with around a half dozen of the original programmers of the ENIAC[4] would disagree that they were only filling a secretary like position.
In reference to my previous comment, I mostly found it surprising that these pioneers didn't lead to more women pursuing CS early on. I suppose it has more to do with the cultural trends that came after the war as you said yourself.
There's definitely hostility. If a prevailing doctrine is straight white wealthy males are the problem, isn't it hostile to people who are straight, white, wealthy, or male?
I suggest you reflect on this and what people say and mean when they talk about topics relating to privilege, power, gender, race, wealth, patriarchy, etc., and you'll get it, too.
And if it were true, it doesn't necessarily mean it's a glut. CS is, to some extent, the new mechanical or electrical engineering. ME and EE are very broad degree programs, with students coming out of the same university with totally different specializations. They may have only taken 50% of their courses in common with each other. CS is (or depending on the school, is going) in that same vein.
No, those two statistics alone don't say anything about the total number of CS majors. Per the article, CS represents ~20% (of students with declared majors).
CS is 214 of an estimated 3500 female student body.
That still seems exceptionally low. Posted this upthread but in 2010 20% of the student body was in Biology (once topical sub-specialties were aggregated).
20% of ~3500 would be closer to `700, which is 3.3x the number of declared comp sci students.
Or maybe my math is wrong? I'm more interested in the actual knowledge being put in and attention being paid out than a critique of the degree naming conventions.
No. Very little of a CS degree is "coding" - CS is so much more than that. It's even beyond "engineering".
A proper CS degree teaches you how to think, how to solve insanely hard problems, and how to do so with a team of other smart people - often with different personalities.
What separates CS from other degrees is that it does filter out those without the horsepower or fortitude on both the quant side (algorithms) and the creative side (systems, architecture).
That means, that even if the SV bubble crashes, CS majors are the best equipped to handle whatever career is hot next - any hiring manager at Goldman, McKinsey, or F500 company X will tell you the same.
Any degree that claims it teaches you how to think should ring the snake-oil alarm.
> how to solve insanely hard problems, and how to do so with a team of other smart people - often with different personalities
So how do they teach that? Or does that just mean they got a few group projects, where smart people bump into each other but don't really learn to solve problems in a team?
Unis tend to suck at teaching teamwork. Though they tend to be pretty good at teaching algorithms and systems (which are good to know, and don't go out of date too quickly).
Well, philosophy more or less stakes its claim to value as an undergraduate program solely on that premise. Whether it actually teaches one to think, what exactly that means, and whether it's possible to teach someone to think who hitherto didn't know how to think, are of course questions that trouble it, but they're all distinct and seemingly empirical issues.
University CS programs are kinda shitty for teaching people how to actually write code. It's not really more than that, it's math and theory and proofs instead of that. University faculty, if they ever worked in a professional environment, did it years and years ago before they got tenure.
The worst course I took in my CS department was the algorithms and data structures course. Didn't write a line of code. Wrote a ton of induction proofs. Learned a lot of esoteric algorithms that have very good big O profiles, but suck bogwater because of cache coherency when they are implemented on non-imaginary hardware, or have high constant factors that got hand-waved away. I'd sign up for that course in a hot second, if it covered the same material, but instead of scrawling on a chalkboard, it was structured around writing the same algorithms in C, segfaults and all. I don't think most CS majors could hack that kind of course, however.
Ivy League student material. Oh, how people flailed when they had to wrap their heads around pointers. These were brilliant people, most of them far smarter than I was, but getting into the nitty-gritty details of things seemed to break their brains.
That's what we call "book smarts." People who can regurgitate trivia to show proof of intelligence, but can't actually think their way out of a paper bag.
I went to Kent State, and Data Structures was all about understanding and implementing trees, lists, and the like, in C or C++. It was super easy since I had already gotten all my segfaults out of my system in high school, but very practical.
Algorithms was all about searching, sorting, and heaps, and the main project was implementing several different sort algorithms in C or C++ and comparing their best / worst case performance. Also pretty easy, and very useful.
Advanced algorithms sucked balls. 100% theory and proofs, no implementation. Instructor was awful Didn't get anything useful out of it. All the other students were cheating on the homework together, since all the problems were right out of the textbook and somebody had the solutions manual. Still got an A but it was awful and I got nothing useful out of it.
That's interesting because the worse course I took was software engineering.
The techniques I learned there are all out of date or things I could have learned in the first few months on the job. While the techniques I learned in algorithms and data structures (and other theoretical classes like discrete math and automata) are pretty much still state of the art and have proved useful time and again (and I definitely wouldn't have picked most of them up after a few months on the job).
"What separates CS from other degrees is that it does filter out those..."
This is quite a strong claim. I also find the terminology "filters out" troubling. I thought universities were fundamentally there to teach people and not just sieve them. Well, personally my physics department was operated like a sieve but that simply is not a rational way to run an educational facility. It's just macho bullshit ("We're so tough...").
"That means, that even if the SV bubble crashes, CS majors are the best equipped to handle whatever career is hot next.."
I would claim when changing to a new field, any university major that requires rigorous thinking and understanding of math based systems gives that advantage.
At Stanford, undergrads are admitted generally to the school, then they get to pick whichever major they like. Most students don't pick a major until sophomore or junior year.
Stanford accepts 50% women and more of those women are picking to become CS majors after they get in, when they didn't just a few years ago. This is actually progress.
To be fair, applicants indicate major areas that they're interested in. The admissions committe may or may not take that info into account in deciding on applicants.
I've noticed very few of these articles look at the recent past ('80s) when women were a significant percentage of programmers. I'm too young but I have the feeling working conditions were much better back then.
> I'm too young but I have the feeling working conditions were much better back then.
You mean working conditions for programmers?
From talking to people who worked in computing back then (like my grandfather), it seems like we have it better today. Of course that's only anecdotal, and my perception of today is as coloured as my choice of people to talk to.
Old people always say they had it worse though. "In my day we had to walk 15 miles in the snow to compile our code." Yeah but rent costed 2 days pay back then, not 2 weeks.
Turns out, it's actually pretty accurate. But food was much more expensive, sucking up maybe ten days of income (and that's 100% groceries, which is rare enough these days, I suppose). Clothing, though, that's where you see the real change. Cheaper these days in non-inflation adjusted dollars than it was in the 1890's, in you can believe it (maybe I buy fewer articles of clothing than most people, but likely not less clothing than people in 1890).
As a foreigner, I guess it is similar to importance of a labor in previous socialism.
Maybe there is some "The Part played by CS majoring females in the Transition from Ape to Man" on the way. Who knows :)
The vast majority of people working in software in the US are men. The statistics, various studies, a mountain of anecdotes by women working in tech, etc. all point to systemic problems of sexism in the industry and society more broadly. There's a growing movement from various corners to try to address fucked up tech industry culture issues in various ways, encourage interest in programming among women, etc. So statistics like these are encouraging.
How many of them are just doing it for money since salaries are high right now? How many of them actually would do it if it paid 50k instead of a 100k?
Not to discourage the female of the species from having fun hacking away like the rest of us do ... but you do make a good point.
Where were the "women in tech" back when computer programming was some "weird" hobby of the outcast nerds? What has always bothered me was that feminists have conveniently painted this lack of interest (prior to the financial incentives of current times) as some evil intent on the men. Sexist industry? Give me a fsck'ing break! All of their perceived sexism is in their own minds.
Plenty of old school programmers were not "outcast nerds" at all, but people who happened to stumble on the subject. The whole nerd thing is something that happened mainly at certain universities and then when computing become more popular in high-schools. Women have far more than men been interested in things that doesn't mean money. Just that if you're a book, arts, craft and/or music nerd it doesn't count. By the way, when did computers ever not bring financial incentives? Back when mostly women did it maybe...
> Where were the "women in tech" back when computer programming was some "weird" hobby of the outcast nerds?
Programming was originally an exclusively female profession because it was seen as lowly-paid "women's work". Later it became a male profession.
But you're talking about the non-professional setting. Well, that started with the home computer revolution. There were few teenage girls programming at home because the means of doing so - home computers - were marketed almost exclusively to boys. Alas, parents seem to avoid buying boys 'girl toys' and vice-versa.
> Programming was originally an exclusively female profession because it was seen as lowly-paid "women's work". Later it became a male profession.
I just glanced at Wikipedia on this topic ... and, apart from the convenient mention of Ada Lovelace at the very beginning of both the articles[1] (makes you curious why they do this), history of programming is evidently a mostly -- no, nearly all -- male profession.
Just what kind of "programming" was it that the exclusively female professional partook on, whose profession was to later become a male profession (and what kind of "programming" are the male professionals partaking on)?
> There were few teenage girls programming at home because the means of doing so - home computers - were marketed almost exclusively to boys. Alas, parents seem to avoid buying boys 'girl toys' and vice-versa.
- Marketers will target whatever that can be easily influenced to make a purchase.
- 'girl toys' are neither superior nor inferior to 'boy toys,' ... and feminists are the last group of people to acknowledge this distinction. As a generalization, girls learn to manipulate people from a early age (hence playing with barbies)[2], much as boys learn to manipulate tools. Toys merely fulfill this instinctual desire of humans; they are not being enforced by the hypothetical patriarchal parents and society.
- Thus, it seems far more likely that despite parents'/peers' encouragement to play more with the tools (such as computers) "teenage girls" continued to opt to play with "girl toys" out of their own instinctual preference. Perhaps because they knew deep down that the real power lies in manipulating people and not computers.
In the early days doing basic arithmetic to count up data was woman’s work because it was a low skill job that only required a person to sit down and know basic 4th grade math.
Female programmers where just people who would rewire the computers do to arithmetic that the mathematicians "programmed". They did not write the algorithms nor did they know anything more than the basics of "this plug does this". their job was taking a work sheet and making the machine do what the work sheet instructed them to do.
as computers automated this the female "programmers" where no longer needed to do this low skill job
https://upload.wikimedia.org/wikipedia/commons/3/3b/Two_wome...
You're extrapolating from a few select examples.
ASCC and many other computer precede ENIAC, and their programming was absolutely not a "women's work".
The history of practical computing is really labour intensive. The mass of the work has been done in counting paychecks of megacorps, census, taxes, and weather simulations. Unfortunately I have no statistics that would say that women did most of the jobs there but based on historical precedence it sounds plausible to me.
Programming as a field has historically two or three subcultures - the corporate, the academic (and finally, the personal).
The academic branch is where the new stuff has been imagined. The corporate branch is where the work that added value to society in form of financial income happened. Think of huge accounting machines, and extrapolate from that to modern computing. Taxes, census etc.
The corporate branch had several tasks that were labour intensive. Usually this labour intensive part was reserved for women (they are more keen on details on average or other such rationalization). Also, historically, women did not get paid as much as men so more labour for the same amount of money...
Women were also extensively hired as data entry clerks.
In the age of the mainframe, a typical division of labour was that the software designer wrote the program on paper with pencil, and then the data entry clerk encoded it into the computer (using punch cards or later terminals).
The integrated software designer / data entry thing probably originated in the universities and other research setings (i.e. Knuth typing his Tex from his notebook the the terminal at his Uni. and so on).
> Programming was originally an exclusively female profession because it was seen as lowly-paid "women's work".
Every time this comes up, someone points out that "programming" was mostly data entry at that time, and that there is a suspicious correlation between the decline in female programmers and the movement of data entry from programmers to administrators.
I can't seem to find hard data either way, though. So make of that what you will.
Actually as an old hand (been in the game since the late 80's) the proportion of women I saw has decreased from when I first started and has only turned around in the last five or so years.
Admittedly this is mainly in a corporate environment, but most of the women I started with tended not to come back when they started their family. I think with more family friendly hours and policies such as remote and flex working this may also change.
To say that "they are only doing it for the cash" is unlikely, as from what I have seen that drive tends to run in men more so than women. cf: all the "web developers" in the first tech boom who did not know shit from clay and vanished as quickly as they came in the bust.
> Actually as an old hand (been in the game since the late 80's) the proportion of women I saw has decreased from when I first started and has only turned around in the last five or so years.
That's backed up by the data. There was an NPR piece [1] with graphs of what proportion of people taking various other degrees and Computer Science were women. They were increasing in lockstep until the 80s, but then after that CS just kept falling and falling, even (to my surprise) into the 2000s.
How many of the people pursuing any career would do it if it weren't for the salary?
(If it bothers you that salaries play a role in how people choose their majors, advocate for an economic system that allows people to pursue their ideal passions without financial worry, whether those passions are in computer science or poetry or "underwater basket weaving" or what have you. Until such a system is in place, though, it's only reasonable that people, in deciding how they'd like the rest of their life to play out, go where the opportunities are...)
I think it's the same with finance, right? Lots of people follow the money --whether it be finance, CS, law, med-school.
Personally I think it's BS for people to tell you to "follow your passion" and also am critical of the "we need people who are passionate about x". Most people work as a way to make a living.
The first thing that came to my mind, is that many girls that are interested in this stuff may now feel more comfortable than ever to enroll in Computer Science, as the issue of sexism is being tackled and talked about a lot.
This is exactly what I think every time someone says "We need to encourage more women/people to study CS." If you're only doing it for the money, you're probably doing it wrong. Studying CS for 3 years does not a programmer/hacker make; staying up coding all night or while other kids are playing outside, for years, is what it takes.
Do we say this kind of crap to Lawyers? Doctors? Engineers? (scratch the last one i'm sure we do say this kind of crap to them)
Why must programming be such a soul sucking life encompassing thing? It doesn't matter if you're a woman or man, this stupid mindset that somehow the only way to be a programmer is to be a stereotype needs to be launched into the sun and forevermore forgotten.
Just today I met a girl that was in her last year for aerospace engineering. She didn't look like any nerd you might think. She just looked normal. Great fun to talk to as well.
Maybe when us nerds stop thinking of ourselves as some sort of promised race of super humans we can move past some of this nonsense.
Tomp, the person you responded to, wrote two sentences. You responded to their second sentence, but the first sentence provides the whole context.
Tomp said they think this way every time someone says "We need to encourage more women/people to study CS". This relates to the whole "the tech industry is sexist" non-sense some radical feminist spew out ... speaking of which, out of the following two which do you think is vital to address (psychologically) first?
- stop attributing the "promised race of super humans" self-perception
- stop attributing the "successful tech men are sexists" projection
Which is causing more strife than the other? Lookup 'github horvath', donglegate ... why even elevatorgate.
> She didn't look like any nerd you might think. She just looked normal. Great fun to talk to as well.
Looks like you're projecting your own ideas and complexes to what I said. Guess what - I look normal as well! But still, my interest in computing goes deeper than finishing class assignments and longer than 3 years.
Most lawyers and doctors don't build stuff. Those that do (do new medical research, or write new laws), I sincerely hope and expect that their knowledge and understanding of their profession goes way beyond an average coprofessional's.
Bad code causes real harm to everyone else on your team, so coders have more incentive to worry about the skill of their coworkers than other professions do. You don't need to be nerdy for that, just good, but the two are correlated because you gain skill if you willingly spend all of your free time on technical stuff.
As for workload, lawyers and doctors tend to be overworked and honestly that's really not okay for doctors, as it leads to dangerous mistakes. My cousin is a lawyer and she always seems to be working, but she's also great at what she does. Another cousin of mine is becoming a doctor and residency is quite a gauntlet for her to run. But those are other issues.
> Bad code causes real harm to everyone else on your team, so coders have more incentive to worry about the skill of their coworkers than other professions do.
There isn't anything unique that bad code inflicts on your co-workers that isn't analogous to the problems faced by most people who have to deal with incompetent coworkers.
You can miss your deadlines due to dealing with it. When you're on call and you get pulled in to clean up someone else's problem. Bad design patterns cause lots of unnecessary duplication of work.
Yes, you can find other jobs where a mistake brings down the whole team, but it's rarely the kind of mistake that can persist in the codebase for years on end simply because there's no budget to refactor.
Now, you might point out that managers can, in fact, cause even more problems than that, but I don't think you'll find many people who want to work for a bad boss, either and I bet you or someone you know knows people who have left otherwise good jobs because of their boss.
Medicine and big-firm law are life encompassing things. Less true of engineering. But for the future doctors, usually pre-med and definitely medical school and being a doctor forces this on you, and for the big firm lawyers, the same.
Right but we're not telling people you can't be a doctor because you didn't sleep and breathe medicine before you went to college.
Least the doctors I have met all seemed to think of it as a job not a lifestyle.
It is that fundamental point I'm slightly annoyed with. Big firm law is also a bit of a clique, a lawyer friend of mine and the lawyers I know of all seem to love law, but aren't of this weird mindset that only the self chosen few are worthy of the endeavor.
I would like to see nerd elitism and nerd bashing both stop.
Some people claim that to be a programmer you need to have a certain personality or hobbies, and this is wrong.
But nerd elitism is also a reaction to having been excluded, ridiculed and sometimes bullied. That doesn't make it right, but it also means that bashing nerds and nerd culture, as is all to common amongst progressives, is both unfair and counterproductive.
What I would like to see more people saying is that it's ok that many people in tech have certain hobbies or personality traits in common, but that a person doesn't have to have these things to work in tech.
They were tinkerers, though. You've got the MIT model railroad kids, all the people that fooled around with scrap electronics, the radioheads, some gearheads.
I have no references to back this up, but I think it would make an interesting longitudinal study, or if you were somewhat cruel, a twin study: are children that spend most of their play time building with Legos or Kinex or erector sets significantly more likely to end up as engineers and computer programmers?
These things don't pay though. People care about diversity only where it pays.
If comp sci. was still seen as a thing for nerds with skin issues that don't get a lot of money you can bet there would be no "diversity" thing going on.
There should be no such thing. Instead of trying to bend ethics I'd rather make sure any one, from any skin color, gender, place of birth, etc. can do anything they want. THAT would be diversity.
The truth is that today what you can do with your life depends a LOT more on your place of birth than your skin color or gender.
A job at McKinsey or Goldman pays far more (risk-adjusted, 7-10 years out of school) than a CS degree does - you can verify that easily. If you're optimizing for money, CS is not the answer (unless you're leveraging it to get a job on Wall Street).
Unfortunately finding a contrary result is a career limiting move. Consider Robert Putnam, who suppressed his research (showing that diversity harms social cohesion) for 6 years while trying to "develop proposals to compensate for the negative effects of diversity".
Here's the abstract from your link. A bit more complicated than your summary.
Ethnic diversity is increasing in most advanced countries, driven mostly by sharp increases in immigration. In the long run immigration and diversity are likely to have important cultural, economic, fiscal, and developmental benefits. In the short run, however, immigration and ethnic diversity tend to reduce social solidarity and social capital. New evidence from the US suggests that in ethnically diverse neighbourhoods residents of all races tend to ‘hunker down’. Trust (even of one's own race) is lower, altruism and community cooperation rarer, friends fewer. In the long run, however, successful immigrant societies have overcome such fragmentation by creating new, cross-cutting forms of social solidarity and more encompassing identities. Illustrations of becoming comfortable with diversity are drawn from the US military, religious institutions, and earlier waves of American immigration.
If you read the paper itself, it's basically empirical work describing the negative effects, followed by an essay claiming the positive ones. As I said - he spent 6 years looking for something to counter his empirical results, and published when he came up with it.
Note also that I'm not strongly endorsing this work - I'm just pointing out the strong desire to not publish a result against diversity.
I think it's obvious that diversity can be both good and bad.
A team where everyone speaks a different language is very diverse, but not effective, since there is no communication. One in which they at least share some common language which for all of them is a second language, not with full fluency, would be able to function, but likely not as efficiently as one in which everyone speaks the same language as their mother tongue.
And language can be just an analogy. Instead of language, imagine a cultural background of shared assumptions and experiences. A shared background can help avoid misunderstandings and speed up communication.
At the same time, it's clear that diversity can help in many ways, avoiding single-mindedness, for example. If everyone has the same concepts and background, they might miss something important.
For political reasons, people like to say that diversity is good, and it is indeed good in some ways. But that's far from the whole story.
It would be better to not use "diversity is good for business" as a slogan, when there are other more valid reasons to fix issues with inclusion where they exist.
It's hardly clear to me that ethnic diversity helps in any way for most companies. Several people at my current company told me they were excited that I'd be providing diversity. I asked them what they thought that would bring them, and after pressing the issue I realized they had no clue.
I have no clue either. Some unique perspectives I bring: I favor rigid APIs over close team communication, I favor Bayesian statistics over frequentist, and I'm working on convincing folks that the JVM is actually a great platform to deploy code on. Are these technical matters something that a certain ethnic group (different from mine) is uniquely single minded about?
I've been the bringer of diversity for most of my career. And I can't think of a time when it's actually mattered.
> JVM is actually a great platform to deploy code on
The JVM is a fantastic platform to build for and run on. I know of nothing else that's so powerfully general purpose for typical server-side business work, with such a compelling ecosystem. Multiplatform support can be useful, though mainly for me it's the ability to develop from any platform, rather than deploy to. It seems to be widely undervalued -- I would describe it as popularly unfashionable right now. Yet I don't know of any platforms with such deep ecosystems and comparable technical merit. .NET comes close (and is arguably better designed in some ways, and has some neat features), but is Windows-focused and seems to lack the open source communities Java has.
Talking about this almost makes me want to start a list of "awesome things about Java that are without parallel in other platforms".
I've enjoyed reading a number of the comments you've posted in recent days. Please continue and good luck with your evangelism!
I agree it might not help in all cases. But ethnic diversity can obviously help in marketing, assuming the target audience has multiple ethnicities, which is often the case. Aside from marketing, it might help less as you get more and more technical, but it might still help in areas in the "middle" like product design, etc.
This is not true. I'm tired of people confusing correlation with causation. The famous studies that people cite shows a correlation between women in senior management and profitability. It is entirely possible that the most competent women are attracted to the most profitable companies.
Given the proportion of Asians in CS/programming, it's probably one of the most diverse industries. Don't fall into the feminist indoctrination that "diversity" only means women or that women are a minority.
It doesn't. Should we include Chinese, Korean, Japanese and Indian people in one bucket? What about those descended from European Jews- are they just white people? With a finer-tooth comb, it's more racially diverse than the prevailing dialogue indicates.
As white people make up a significant portion of the population this just explains demographics more than anything. You might also correctly guess high-paying industries in Japan are dominated by Japanese people.
What's with the obsession of gender equality by women in high paying jobs?, is never about lack of women in sewer maintenance or coal mining, or bugs exterminators, or firemen (firewoman? Is that even a word?). Is always CEOs or STEAM jobs at silicon valley. That's a very narrow and convenient definition of "equality" isn't it?
Believe it or not, women have had to fight for the right to work in coal mines. You probably hear only about the fight to get more women in tech, since you are in tech. But anyway, here you go: http://www.women-in-mining.com/news/1389309
Proof that there used to be laws on the books banning women from working in mines, and feminists went and fought them. It's quite possible that the other reason you don't hear about female coal miners asking for more representation is that tech is worse at hiring women than coal mines are by now.
It's not even about the lack of women in undesirable male dominated jobs.
What about the lack of women in relatively high paying skilled trades like electrician or elevator repair?
I think you'd get more bang for your buck by funding programs to help working class women move into skilled trades, than by trying to move middle class women who are already going to college from one major to another.
Because CEOs and other higher paying jobs impact the world we live in. Women need to be represented in high impact jobs so that we don't have a world designed entirely by men.
According to the article "It was unclear if Stanford is the only major U.S. university where computer science is the top major for female students."
That link was the top hit for https://www.google.com/search?q=mit+women+enrollment
This is a pretty sad thing to see in something purporting to be journalism. I can't blame the really writer though. They probably only had 30 minutes to get something out the door to drive their view count...