[whateveridunno]

She didn't say "all women", she said "many women." I attend the University of Texas at Austin. I started out as a CS major, still am, but no longer want to work in the field. One of the reasons was the fact that although I'd taken AP CS courses in high school, I still felt looked down upon because I'd first been exposed to and developed an interest in CS "late". This attitude came from my peers, the companies that attended our career fairs, and even from my first exposure to the online tech press/blogosphere- I remember reading an essay by Paul Graham wherein he essentially implied that if a woman hasn't started coding by 13 all hope is lost for her. The only people I didn't get that impression from were (most of) my instructors, but that wasn't really enough, especially in the 500+ person intro classes I was in at the time.

Incidentally, like many women in CS, I was encouraged to look for role models among other women in my department and in the broader tech world. Dear other technical college women, if you're reading this: Don't. In my personal experience, successful women in the field are much, much more likely to have had parents who were programmers and to have started earlier. All the women who were pointed out to me as role models had this background. It was only when I started looking to the successful men in my program that I started to find people who had first learned to code in their sophomore years and decided to stay. I have my own theories as to why that imbalance exists, but the simple truth is, I could have learned a lot more about how to "catch up" from those men than the women I was pushed towards.

[SudoNhim]

I understand the feeling of needing to "catch up" to fit in. For the first three years after I started programming I kept my work almost completely private, I felt so far behind. I wrote several hundred projects that I never showed to anybody, and didn't even keep. I still feel the gap a little bit today (five years in), but it seems mostly gone.

I fit the programmer archetype exactly, and it took me three years of near constant engagement before I felt I could even begin to fit in (culturally) with experienced programmers. I can easily imagine the task is considerably harder if you don't fit the archetype.

On the flip-side - the desire to "catch up", and the solitary nature of the challenge lent me considerably more motivation and creativity than I seem to have now that I have "acclimatized".

----

I'm very interested to see how it is going to turn out for my sister. She's a very talented programmer, but she doesn't try to immerse herself in the culture of it at all, rather she is treating it as an auxiliary skill to her studies in GIS. I feel some smug satisfaction knowing she is coding circles around most of the guys in her classes, despite not taking on the identity of "I am a programmer".

[Alex3917]

> I started out as a CS major, still am, but no longer want to work in the field.

Working in the tech field has almost nothing to do with CS. Many/most developers don't study CS in college, and technical ability is only a very small part of what makes a good developer.

[ahallock]

> I still felt looked down upon because I'd first been exposed to and developed an interest in CS "late".

Come on, there are assholes everywhere who use this tactic to make themselves feel superior or to get rid of potential competition, men and women alike. This is not exclusive to CS. A lot of people are worried that they put so much time into something and that someone 'fresh' could make them look bad by picking it up quicker. It makes it that much more satisfying when you beat them.

[whateveridunno]

If it was just a small minority of men in my program, I would have agreed with you, but this attitude seemed also prevalent- and I could be wrong about this- in companies and the larger tech world.

One thing I noticed in particular, was that a hell of a lot of "diversity initiatives" (stuff like code camps, scholarships to diversity conferences, etc) set up by companies like Square and Google and nonprofits like Grace Hopper gave their opportunities mostly to minorities who were already very successful, with internships in prestigious companies. If even the programs explicitly meant to increase the percentage of women/minorities in the industry go largely to very experienced people, I thought at the time, then there's really no hope for me at that point.

In any case, none of this is what led to me deciding I didn't want a tech career, it was just a contributing factor. I probably could have pushed through it, but I realized I didn't like tech enough to do so- I liked coding well enough, but I didn't like or value the work most tech companies were doing.

[jdcarter]

I have to agree that there are a lot of bad programming jobs out there, but there are some really good ones, too--many times in places that aren't obvious. I'm speaking only from my own experience here, but I'm currently working at a big-name company and they pay well but the work is boring as hell and the culture is not to my liking. I've worked at smaller/no-name companies and had a vastly better experience--more diverse work, more opportunities to develop new skills, and a much friendlier culture as well.

If you have any interest in staying in the field--and I hope you do--don't limit your view of potential jobs to just the high-profile companies. Talk to some of the smaller shops around, you might really like what you find.

[Khaine]

On your diversity note. I find it amusing, since when I was at collage the diversity push was all for women, so unless you were an exceptional student all of the scholarships went to women. And now it appears to be being pushed to a smaller and smaller subset.

I hope that you've found something you enjoy to go into a career in. I know I studied tech and now work tangentially to it, and sometimes I feel like I made the wrong choice.

[ssmoot]

I played around with a Franklin PC 8088 when I was a kid for a couple years that we had it. I tried BASIC but never got close to my goal of writing a Tic Tac Toe program. Didn't know how to read input. Didn't even know that the "^" on the "^SAVE" menu item at the bottom meant to hold down CTRL, so my "programs" never survived more than the hour or two I tried (mostly in vain) to get something to work.

No one in my family or peers really knew much about computers and while the Apple IIe at school were much more impressive, that was just playing trivia games and such. Not writing anything ourselves.

It wasn't until I was about 16 that I touched a computer again. Built my own eventually to play DOOM. I didn't know anything "technical" at that point beyond autoexec.bat and... config something. I forget the other one.

It wasn't until I was 21 that I did my first real "programming". Which consisted of reading a book on HTML and being paid $5/hr by my father in law to write some truly bad markup while he did the real work.

I picked up some books on c#, ASP.NET 1.0, MSSQL Server and did my best to absorb what I could. My father-in-law didn't know/work-with most of that (he did help me figure out some SQL basics though) and I didn't have a peer group or support system or anything. About a year later I had a job paying about as well as Home Depot might writing c#.

Almost 20 years later I'm writing Scala and make a good living.

I don't say this as advice exactly. Just saying the "you can't start late" stuff is bullshit. I've often regretted not having access to college so I could answer "write a binary tree on the board" questions. So I didn't feel inadequate in those ways. But it hasn't stopped me getting a job and I'm overall pretty satisfied with my career (well... there was a dark time when I attempted to manage that was pretty cringe worthy) and accomplishments.

I wish I had something more to offer people who think a career in tech is out of their reach because they couldn't afford college, or they started too late. All I really have to offer is this:

Pick up a book. Remember how practically no one actually read a text-book from front to back in grade school? If they had they'd have had a huge advantage right? Pick up a book. Those that say "I learn by doing" will never ever ever be exposed to the same depth or amount of knowledge as you'll get from the condensed, edited brain-on-paper of accomplished authors. Be well read. It's like cheating. And it's cheap. Often even free (Not talking Blogs. Those are mostly only useful for very specific questions/topics; I'm talking about the free Ruby book, or beg for a copy of haskellbook. Or torrent if you must and pay them back for it later).

My 2c.