She didn't say she was put off by competition, she said she was put off by competitive language in the job listing. She recommended more focus on the collaborative side of the internship - mentorship, line by line code review, and being part of decisionmaking. "Things that have to do with collaboration and learning appeal a lot more to female candidates."
Couching something in mainly competitive terms does not just advertise that it's competitive, it also hints that there's a sort of pissing contest atmosphere at work. In the case of Fog Creek, it was an inadvertent, false signal, but what this woman is saying is that it's a negative indicator many women watch out for.
You can be at once highly qualified for a competitive field and drawn to that field for reasons having nothing to do with competition. Those female premeds are almost certainly more interested in working with patients than in beating their chest and bragging about how they got into a good med school. (And I'd venture the same holds true for the males.)
CS is one of the very few industries i've ever been been around which engages in the "i'm better than you" pissing contest, EVERY SINGLE DAY, and yet asks itself why everyone looks the same.
I really do hope that at some point, we lose our sneer and arrogance and stop thinking that we're better than everyone just because we have some kind of exclusive skill that's alien to most.
I would add that in my experience, men who routinely engage in this kind of pissing contest are more likely to come across as "sexist pigs" in some sense. I've been in social situations where the signal was "you can't run with the big dogs, you are just a girl". Having good computer skills does not guarantee that one has the social savvy necessary to find the right way to deal with that kind of message.
In fact, if "typical" girl programmers are anything like your stereotypical boy programmers, it may be that they are highly likely to lack such skills. There have been a number of articles posted to HN where women in the industry complain about these sorts of issues (while I read between the lines and wonder how she could have done something so dumb given the context) and I do kind of get the impression that most women really don't know how to effectively deal with stuff that may not really be intended as sexist but is frequently just kind of juvenile (for lack of a better word).
Indeed, I never after for a job which is worded competitively.
I done a lot of contracting over the years. Usually 3-6 month placements and I've learnt to spot a company culture from the ad. Sort of like after you've been looking at house ads for a while you start to understand the lies that are going on.
Disclaimer: before reading on I'm jaded and bitter from years of dealign with a/holes, liars, and bad contracts. So its best to make up your mind as whats suits you. But my learnt experiences:
Worded competitively usually means you are working for a money first workplace, and the boss will usually be sleazy sales men.
with it you get extremely short times lines, under cutting competition, lots of pressure to finish perfectly first iteration (i.e. no time to refactor code which organic grew as you worked), and any bugs in the first and only iteration are a big deal... many projects I've worked on just don't have a testing cycle or bug fix cycle. They chew developers up and make them bitter and cynical.
The other ones to watch out for are ego stroking, the old "rock star developer". Thats usually a sign when over times come they will to pay you with ego rewards instead of money. The play will use every manipulative trick they can think of get you to work for free, and make you think you are doing it because you love it. Don't fall for that, working is a partnership and they need to offer you the respect and payment you deserve, even for work you like doing.
Buzz words are a keen sign you are going to be working with a bunch of sales men. It can also mean its a design agency who don't under stand what they are saying.
For example I've been to some great interviews listing HTML 5 as a pre-req ... where 10 minutes in I've been trying to end the interview and escape. When they tll you they are building every website in AJAX, MVC, REST, and HTML 5 head for the door.
IMO that is showing a lack of understanding of technologies and a failure to do proper analytical process into work. Firstly HTML 5 doesn't have great legacy support, its pre-mature in my mind to be using it for a lot of work especially considering most of these people are build simple ecommerce and brochure sites... often meaning yoga re dealing with small businesses who can't afford to retro fit when they discover 20% of the user base can't complete purchasing because of IE 6. Mobile is a different story its ready, but thats the analytical process, choose the right tool, and if you see people nailing in nails with nails walk away.
Another two which go instantly on my nervous list are gloating about team culture or how great the office is. I don't let these stop me chasing a job, but I do get extra cautious when going threw the interview process that those items are intact true.
Because in 15 years of programming I've never really had a bad team. A few toxic characters for sure, but most teams are great. Often it can actually be a good sign, they are after team fit, and that can be the best thing ever.
Most developers are just normal average people, usually with one freakishly intelligent person, and a few play doh eaters. "Amazing" teams often have several gifted people, and I don't like working in those teams to much, conflict always arises because people have cleverly thought of a solution, and instead of implementing they fight. I prefer normal teams with mixed backgrounds and age spread, so water cooler talk in the office is at least interested and I find I bond better with genuine people, and that makes them easier to deal with because I can approach them problems and negative issues.
I won't take a position with a crap office full stop, I'm actually effected by environment. So before accepting a job I ask to see the offices. Its extremely important to me.
In saying that I'm not sure what it has to the work advertisement, it usually sets off my paranoia that either the job is boring as hell and they couldn't think of anything else for the ad. Or the complete opposite they have built an nice office to stroke your ego, or compensate for work overload.
Buzz words are a keen sign you are going to be working with a bunch of sales men.
The prejudicial reaction to buzz words is one of the things that I've found really weird in the programming fields. Often, a buzz word was a legitimate technical term just a few years, or a couple of decades ago. It's not the word, it's how it's used. Rejecting someone because they use a given buzz word is just prejudice. It just means you're selecting those people who are so aware of the march of buzzwords, they don't use the stale ones. In some cases, these will be savvy programmers. In other cases, this will be skilled users of word salad.
Buzz words shouldn't trigger a decision. They should trigger questions.
I know where you're coming from, and you are right. Its context. I find buzz words tend to upcoming marketing terms, perhaps we are discussing slightly different things.. not sure. Older buzz terms aren't a problem as they have either been stabilized or rejected.
But where you see "savvy" I generally see naive.
I find people that get hooked up on buzzwords are younger people trying to make a mark and people trying to cash in. Been that demographic myself, been burned, and I watch others burn to this day.
I'm seen so many millions go down the drain to buzz terms and over sold open source initiatives. But then again thats why I put a disclaimer saying I was bitter and jaded LOL
> The prejudicial reaction to buzz words is one of the things that I've found really weird in the programming fields.
At one level, like Google aggregating signals, responding to an abundance of buzz words is one of several ways to classify a given posting as promising or not. A few buzz words could be fine, but a company actually saying they "are building every website in AJAX, MVC, REST, and HTML 5" all in the same sentence is definitely problematic.
Separately, I think there are people who use buzz words to earn points among their non-technical colleagues, which seems to be cultural appropriation from programmers. You can also see this with words that have been redefined in pop culture, like 'hacker'. This naturally breeds resent and wariness of buzz words in general.
I thought when you said you find it really weird, that you didn't really understand it, or the reasons behind it. Now, it seems you do, and you simply think it's irrational? Irrationality in humans and their dealings is not something I find particularly weird anymore, in myself or in others.
What you call "Buzzwords" many would call technical jargon.
Jargon is a shorthand way of communicating quickly with others who understand it.
You see "Buzzwords" in are building every website in AJAX, MVC, REST, and HTML 5, where as I think "I wonder if the MVC is a front end Javascript MVC framework operating against the REST backend, or if the model & controller parts are shared by the REST and AJAX front ends, but have different views?"
I know you meant it as an example, but to me it was a perfectly legitimate description of a development stack.
Theres a definite difference between a framework description and a buzzword over loaded blurb, placement in the ad for example can change the tone of the whole message.
So starting with "we are an HTML 5 AJAX shop..." I would roll my eyes, where as compared to "Our stack makes heavy use of REST methodologies..." I would mull the description.
I guess its a level of understanding that goes into the use of the terms.
My post was not about the specific buzz words, which is why I borrowed the example from the grandparent.
If I were describing a technology stack, it would include the actual development language and further specific, relevant details. That might include the exact example as given, but the example standing on its own still ranks low on the desirability scale.
Also, my description would exclude "building every website in".
Yeah I find getting work hard now, not because I can't get the jobs, but because I don't want to work in a lot of places. Getting old I suppose, lost the drive.
You have to take those jobs to find your niche sometimes. Thats why I put the disclaimer at the top, its my point of view, everyone has to find there own, find what makes them happy. Some people need there egos stroked, some people love high pressure, everyones different.
Having the courage to quit is a big thing, I remember the first time I quit I almost vomited, my last job I was yelling at a director of the company. I had the courage to stand up for myself and faith, but you have to earn that, most people aren't born with it.
Networking has always been the best for me, every big break I've had has been over a drink at the pub. Which is easy for me as I'm an extrovert and have a good sense of humor, so people take a liking to me.
But theres way to network if you're not extroverted, I attended programming groups and go to presentations, heaps of my friends don't leave the house except for those meetings.
Theres heaps of tips about helping in community projects (even just testing), twitter, a blog.
Infact friend of mine got head hunted for £300,000 because he ran a blog and had become a subject matter expert on security and identity, so ads aren't the only way.
For the love of good don't let me put you off applying just because Im bitter and jaded ;)
Couching something in mainly competitive terms does not just advertise that it's competitive, it also hints that there's a sort of pissing contest atmosphere at work. In the case of Fog Creek, it was an inadvertent, false signal, but what this woman is saying is that it's a negative indicator many women watch out for.
You can be at once highly qualified for a competitive field and drawn to that field for reasons having nothing to do with competition. Those female premeds are almost certainly more interested in working with patients than in beating their chest and bragging about how they got into a good med school. (And I'd venture the same holds true for the males.)