Text of martinfowler.com › articles › born-for-it.html as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Born for it

Born for it How the image of software developers came about The stereotype of the socially-awkward, white, male programmer has been around for a long time. Although “diversity in tech” is a much discussed topic, the numbers have not been getting any better. On the contrary, a lot of people inside and outside of the IT industry still take it for granted that this stereotype is the natural norm, and this perception is one of the things that is standing in our way to make the profession more inclusive and inviting.

So where does this image come from? Did the demographics of the world's programmer population really evolve naturally, because “boys just like computers more”? What shaped our perception of programmers? This text is about some possible explanations I found when reading about the history of computing. 20 April 2016 Birgitta Böckeler Birgitta Böckeler is a developer and consultant with Thoughtworks in Germany. As a Technical Lead on custom software delivery teams, she is splitting her days between coding, coaching, consulting, and keeping the work fun. diversity computer history Contents Coders Nobody saw it coming Born, not made A self-fulfilling prophecy “I guess I think I’m more balanced” “My God, this is so easy.” A single model to identify potential programmers So what can we do about it?

Be aware of “similar-to-me” bias. Stop acting so surprised! Challenge the image of the “real programmer” Diversity is the real rock star Coders Nathan Ensmenger is a professor at Indiana University who has specialised in the social and historical aspects of computing. In his book “The Computer Boys Take Over” , he explores the origins of our profession, and how programmers were first hired and trained: Little has yet been written about the silent majority of computer specialists, the vast armies of largely anonymous engineers, analysts, and programmers who designed and constructed the complex systems that make possible our increasingly computerized society.

The title of the book is a reference to where it all started: With the “Computer Girls”. The women programming the ENIAC — one of the very first electronic, general purpose, digital computers — are widely considered to be the first programmers. At the time, the word “programmer”, or the concept of a program, did not even exist yet. The six women (Kay McNulty, Betty Jennings, Betty Snyder, Marlyn Wescoff, Fran Bilas and Ruth Lichterman) were hired to “setup” the ENIAC to perform “plans of computation”.

More specifically, they were teaching the machine to calculate trajectories of weapons, to be used by soldiers in the field. The ENIAC women were recruited from the existing groups of women who up until then had been calculating these plans manually. The Computer History Museum in Mountain View has an interview with Jean Bartik (formerly Betty Jennings) on their website that offers a glimpse into the way Jean and her colleagues approached the task.

The most fascinating thing for me is that Jean Bartik describes how those very first programmers already appreciated the value of pair programming, a concept that took more than 50 years (and Kent Beck’s book, “Extreme Programming” ) to get its name: “Betty Snyder and I, from the beginning, were a pair. And I believe that the best design and all that stuff is done by pairs because you can criticize each other, find each other’s errors, and use the best ideas.” -- Jean Bartik Computer “setup” was of course a very mechanical process at the time, pictures from those early days show how much it resembled plugging cables into telephone switchboards.

So this work was seen as handicraft and mechanical, as opposed to scientific and intellectual. The women were called “operators”, “computers”, or “coders”. According to Ensmenger, the term “coders” became very associated with mechanical or manual work, and with the female gender. Even after the term programmer got established in the 1950s, for a few decades to come, “coder” still had negative status and gender connotations, and male programmers tried to distance themselves from it.

Nobody saw it coming If the ENIAC’s administrators had known how crucial programming would be to the functioning of the electronic computer and how complex it would prove to be, they might have been more hesitant to give such an important role to women -- Jean Bartik So the computer revolution had started - hardware was continuously improving, and a lot of people were excited about the progress and the bright future of computing.

But nobody was actually paying much attention to software yet. Stephanie Shirley, who founded one of the very first British software startups in 1962, looks back in this TED talk , saying: “Software was given away free at the time with hardware, nobody would buy software. Certainly not from a woman.” But it turned out that the challenge of software development had been sorely underestimated - they found that programming is hard.

Maurice Wilkes, a pioneering British computer scientist, realised at the time “with some shock and dismay” that “a good part of the remainder of [his] life was going to be spent in finding errors in [his] own programs”. The media in the 50s and 60s also picked up on this. There were stories in the press like that of the Mariner 1 probe to Venus, which left its course and had to be destroyed. The urban legends for this failure include a story about a “.” instead of a “,” in a Fortran statement, or a “missing hyphen” in an equation.

There is no evidence that Fortran was even used in the programming of the probe, but these stories strengthened the opinion that only the most skilled programmers should be employed, because programming was so error-prone. Born, not made It was hard for companies to figure out what skills were needed for this totally new profession. They needed programmers to be really good, because they were panicking about errors. At the same time, they had no specific idea of the necessary skill set.

Companies started to think programmers had to be „born, not made“, and that programming was a „Black Art“. This was fuelled by the fact that programming was a very idiosyncratic activity at the time, almost every computer operated differently. How do you recruit people for a profession like that, when at the same time the demand increases rapidly? The “software crisis” had started. One approach the big players in the industry took at the time to identify and recruit programmers were aptitude tests.

These tests were supposed to filter for traits thought essential to good programming, such as logical thinking and abstract reasoning. According to Nathan Ensmenger’s research, by 1962 an estimated 80% of all business used some form of aptitude test when hiring programmers. Half of these used the IBM PAT (Programmer Aptitude Test), which would become the industry standard instrument. In 1967 alone, the PAT was administered to more than 700.000 individuals, it was basically the gateway into the programming occupation.

1 1: There seems to be no proof that the scores in the IBM PAT actually correspond with real-world programming performance. Most employers did not even check, and the small percentage that did could not conclude a relationship. ( The Computer Boys Take Over ) But these aptitude tests were not enough for some companies, they were also trying to find personality profiles to predict which type of people had a good chance to become happy (and therefore effective) programmers.

One of these companies was SDC, hired in the 50s by IBM to work on one of the largest software projects at the time, the SAGE . In 1956, about 700 programmers were employed by SDC, which was about three-fifths of the available programmers in the US at the time. Only 5 years later, they had hired 7000 more. They say about themselves that they “trained the industry”. To become bet

The rest of this page is on the live site.