Sofia V.

1960s

A primary source of storing data at the time was “punching” the information onto cards. This was considered clerical work, and a keypunching operator position was a common job for women in the 1960s.  Here a woman is shown punching data onto cards.

For more photos and details on the evolution of the punch card and the people who worked these computers see the The Punch Card’s Pedigree page.

Photo courtesy of International Business Machines (IBM) Corporate, circa 1965.

Photo courtesy of International Business Machines (IBM) Corporate, circa 1965

 

 


 

Advancements in technology during this time helped make things such as air travel more efficient. SABRE, one of the most widely publicized and influential computerized reservation systems, was co-produced by American Airlines and IBM. It was used starting in 1964, and it was often operated by women as shown in the picture below.

To read more about SABRE and its role as technology, see the Mainframes in Daily Life page.

Women operating SABRE. Photo courtesy of IBM Corporate Archive, circa 1964.

Women operating SABRE. Photo courtesy of IBM Corporate Archive, circa 1964.

 


 

Programming for new computers was a slow and tedious process. This was aided by tools such as the flowchart template seen below, which helped make writing a large program simpler.  The image below shows an IBM programmer mapping out instructions using the flowchart template to display a logical flow of the program.

For more information about the progression of programming in time, see this Higher Level Languages page.

Photo courtesy of IBM Corporate Archive, circa 1965.

Photo courtesy of IBM Corporate Archive, circa 1965.

 


 

 

Women around the world were involved with technology: the picture below shows a woman working at TeleMisr, an Egyptian state owned television set manufacturing plant. In this plant, nearly half of the six hundred employees were women.

To find out more about labor culture and history through time, see the Rutgers University library page for an index of sources.

Woman operating a television set manufacturing plant (circa 1963).

Woman operating a television set manufacturing plant (circa 1963). Photo courtesy of egyptindependent.com

 


 

The role of the female typist, sometimes called a “girl operator” in technology was seen as clerical work and not a part of the “higher” thinking jobs in tech. Here these advertisements depict the computers as being simple enough for a mundane person to use by showcasing a typist as the main user. Although women in these roles usually did much more than secretarial work, and were mostly immersed in the technology that they used, they were not recognized for being technologically literate. They were most likely stuck in the preconceived notions of basic clerical work.

For more on the history of women in computing in Britain between 1950-1970, see Marie Hicks’ blog.

From left to right: An advertisement for the "Susie" machine and an advertisement for the Baric (circa 1967).

From left to right: An advertisement for the “Susie” machine and an advertisement for the Baric (circa 1967). Photo courtesy of Marie Hicks blog.

 

 

Interview with Dr. Kimberly Hambuchen 10/08/2014


(0:12) Did you play a lot of video games when you were younger?

I didn’t, I had this conversation at lunch today and somebody was telling me you obviously play some kind of game, I don’t know. I played Nintendo Super Mario Brothers and that was it. I take that back I did play quite a bit of Atari when I was very young. But I was’t like a gamer. I would not call myself a gamer at all. I actually went to arcades and played the big machines, that was big when I was in middle school. So I did that sort of thing, everybody did that. So no! I really didn’t.

(0:52) We were all wondering about it because you said that joysticks were used to control the robot’s movement.

Yeah and you know honestly I makes me crazy to run these robots, I just ended up in this position because that’s the software I develop, but it makes me crazy. When I can hand it off to somebody off I’m like yee-haw you go for it just make sure you don’t crash the robot. So it’s not really that I enjoy the running of the robots so much it’s the human interaction side. How do we make these robots easier to operate.

(1:24) Would you say that’s one of the most rewarding aspects of you job? What would you say is the most rewarding and whats the coolest technology you’ve ever used?

I mean I going to nerd out and say coming and doing things like this, getting to spread the word on what we’re actually doing, especially when we have little kids come, and girls who are really interested in robots. They want to participate in their first robotics team but they don’t know if they just want to hang out with all the boys, they don’t know. Seeing girls get really excited to see another girl telling them about you know what she does in robots and this advanced work, so thats really the best part of my job. And i get to do that a lot because we do a lot of tours at NASA. Coolest technology, I was recently blown away by something we did, I want to say it was when we finally got Valkyrie walking and it actually walked over to something, like a valve, and it turned the valve, we were all just stunned, we couldn’t believe it was actually happening. So really that robot, in the time frame we put that thing together, I can’t believe we did it and actually made it do some stuff, you know, more than some other teams actually were doing at the competition, so Valkyrie is a really cool robot, its gorgeous when you see it move it also is mechanically and control wise, which is getting really technical, it is the best robot we’ve ever built.

(3:24) And she’s a she, which is original in itself.

That was someone’s idea on the team and we were like thats beautiful, that’s a brilliant idea lets go with it. I would say Valkyrie is probably the coolest piece of technology I’ve seen so far.

(3:41) And speaking of Valkyrie and the failure you experienced at the DARPA competition, what kind of advice would you give to young students, especially girls, because a lot of times girls will get into math or computer science classes and they’ll get impostor syndrome, where they feel like they’re doing worst than everyone else. So what advice would you give them about accepting failure and learning from it?

I have lived impostor syndrome for years, its only in the last few years, that I was like okay you can stop doubting yourself, you’re not pulling the wool over anybody’s eyes. I think it may be a process of maturity, because I also know a lot of guys that I work with who still are like, somebody is going to figure me out soon, I think its a personality type, because I know a lot of guys who think they’re the greatest and they don’t know jack. They don’t know what they’re talking about, and I also know women who do that too. I don’t know how you get the experience into someone to tell them that they really are good enough, earlier than they’re going to experience it. I don’t really know, just at some point in your life you will realize you belong. But the failure thing its, in robots everything we do is a team effort, so the failure was everyones and its a lot easier to deal with when your entire team has failed. You’ve got people who can finally start to make jokes with you when you’ve stopped drowning your sorrows. Almost everything I do in robotics is a team effort, most of the time failure is a combination of everyones failures. It’s pretty easy to deal with failure when you’ve got a bunch of other people who are in your same boat. It’s not just one person who caused the failure, its a collection of issues that developed over a specific period of time, but then personal failures well I screwed up that, just keep chugging along. I don’t take set backs very hard or personally, but then I also don’t really celebrate the huge major achievements like I should, which is part of the impostor syndrome, they’ve never really effected me that badly, everything I’ve screwed up or failed at was, so cliche, a learning experience.

(6:45) Is that the advice you would give students, young girls especially, you just kind of learn from you failures?

Exactly, just go out there and do it jump off the bridge, because what’s the worst that can happen, I mean you fail and then you move forward.

The Complexity of Women Helping Women In the Tech Industry

When looking at the numbers of  women in technology, especially computer science, we find that they are far outnumbered by male associates and CEOs[1]. And it can be discouraging for women pursuing careers in this industry. This is particularly applicable to the female entrepreneurs at the investment stage of a new technology company. For example, when pitching to an audience full of male investors, women are often turned away without real consideration for their products or ideas regarding technology, simply because they are female[2]. One straightforward solution to this problem is that women should pitch to women, or rather startups that cater to women, and they will have better luck. While this might be true and very beneficial to female entrepreneurs, it is a complex solution.

This solution appears beneficial on a surface level, but in reality it also reinforces women as the “other” in the world of entrepreneurship and startups. It almost gives male investors an excuse to push aside female startups and direct them to female investors. Many women realize this and openly acknowledge that this furthers the idea that women can’t thrive in a male-dominant field.  In the article by Issie Lapowsky, “This is What Tech’s Ugly Gender Problem Really Looks Like” from Wired, Danielle Weinblatt, Founder and CEO of the company Take the Interview, admits she is frustrated with this so-called solution[3]. Before she closed the deal for her company, Weinblatt was often redirected to female investors. She understood this was meant to be a solution to her being turned down by male investors, but it made her “feel like being a woman is something to overcome”.[4] In other words, it might be comforting for women to seek other women on the grounds that their gender won’t be held against them, but it also means that women are unable to break through the “bro-culture”.

Part of the complexity of women entrepreneurs seeking funding specifically for women, is admitting that we need these companies. There are empowering and progressive intentions behind these companies[5]. Yet at the same time, it says something about how women may not be able to go past this. Women should eventually be able to pitch to male investors without any concerns that gender could hold them back.  According to Scarlett Sieber, vice president of Operations at Infomous, if we keep business exclusively between women, we aren’t making as much progress as we could if we included men[6].  If there was a balance of sorts, perhaps as long as we encourage female and male investors, it won’t necessarily be understood as a handicap to some. As we have often said in class, in order to make some major changes, we have to start small. Perhaps starting small means admitting that sometimes women need to help women, while also including men in the conversation about the gender gap.

[1] Miller, Claire. “Technology’s Man Problem”. New York Times. 5 April 2014. Web 16 Sept. 2014

[2] Lapowsky, Issie. “This Is What Tech’s Ugly Gender Problem Really Looks Like”. Wired. 28 July 2014. Web 16 Sept. 2014

[3] Lapowsky

[4] Lapowsky

[5]  Casserly, Meghan. “Tipping the Scales: Women Angel Investing Reaches All-Time High”. Forbes. 25 April 2013. Web. 16 Sept. 2014

[6] Sieber, Scarlett. “Including Men in the Conversation About Women”. Huffington Post: The Blog. 02 June 2014. Web 17 Sept. 2014.

Create with Code: Apps, Web and More

New name: CSCI 1300 Create with Code: Apps, Web and More

Credits: 3 hours

Short description: The 15 week semester is divided into 5 week parts with one project every 5 weeks. These projects include: Scala (or some basic coding introduction), App Inventor (app development), and Web Development. Once a week, there is an in-class workshop, where students are allowed to go around the room and view each other’s developing projects. This workshop helps to unify the class, fight the bro-culture in tech (because everyone is supporting each other), and develop ideas. There are no tests just project check- up. There can even be a humanitarian aspect, or you could even have an overall theme. But really, the course should inspire creativity and develop computational thinking skills. At the end of the semester students will have basic coding understanding, will have created an application, and will have a personal website for themselves to use in the future.

Why: This course is needed because it encourages everyone to establish a basis of code literacy, which is necessary in order to understand our tech-focused world.

Prerequisites?: There would be no prerequisites required for this course and it would be a part of the Common Curriculum. Therefore, anyone would be able take this class at any time throughout their career here at Trinity.