afitz0

What does this provide that isn't already provided by the official AWS CLI?

http://docs.aws.amazon.com/cli/latest/reference/s3/index.htm...

I don't understand why this post has anything to do with encouraging young girls to enter science and engineering fields. Rather, I read this as the musings of someone who doesn't like their current job and doesn't feel very comfortable around the stereotypical engineer type. To that end, nothing in this blog post is specific about why you [the author] feel it's necessary to discourage leveling the gender ratios in our field. I understand that [male] engineers more often than not make disparaging remarks, talk non-stop about the latest (or sometimes the oldest) technology, and are overwhelmingly socially inept, but this is not a reason to stop trying to get more women into STEM. In fact, I strongly believe in the contrary: having more women in the tech industry will greatly improve working environments, reduce the social awkwardness about being a woman in this field, and make the field that much more interesting.

In the end, my take away from this post is exactly opposite from the purported thesis. The author's experience leads me to believe that we should absolutely be encouraging young girls to enter tech. Yes, it might be painful and lonely now, but if you start scaring girls instead of encouraging them, nothing will ever get better.

We're engineers; our jobs revolve around building efficient systems by finding the weak points and fixing them. A major weak point in the engineering system itself is a lack of women. This needs to be fixed.

[Edit for typos]

A big part of me has to ask: Why do we care? Any software engineer worth his/her weight should be able to pick up any language they need on they fly. A posting asking for a specific language is either catering to HR search terms or is indicative of the narrow mindedness of the managers writing it.

I personally care significantly more about the actual projects involved and in what part(s) of the project's life cycle the role encompasses. Even if it's a position coming into a well-established project (and is therefore firmly rooted in N language(s)), I don't care: I'll pick up whatever needs to be picked up when the job starts.

Sure, checking out today's most popular languages is fun and has it's own appeal, but aren't there better data sources?

The not-for-profit I do work for has a lot of similar-sounding exercises. They're all written in Java (right now), but I'm working with our devs to get lots of them converted to JS/HTML5.

http://shodor.org/interactivate

Drop me a line; I'd be interested in what you all are working on.