A woman named "Steve" – IT pioneer, entrepreneur, philanthropist (2019)

Computer museums and preservation

• Multiple comments praise the Computer History Museum (Mountain View) as “amazing” but note most machines are behind glass; keeping them running is described as hard.
• UK museums (Centre for Computing History in Cambridge, RMC Retro) are cited as more hands-on: visitors can use most machines, play games, run software, and see things like the “megaprocessor” running Tetris.
• A hardware restorer’s work at CHM is recommended for those interested in keeping old systems alive.

Early remote programming and tooling

• 1960s/70s “WFH” is described as writing programs by hand, then using punch cards or optical cards and batch processing, often via third‑party bureaux with multiday turnaround.
• Time on mainframes was expensive; careful manual reasoning and code review were essential before running jobs.
• Punch-card typing was sometimes done by dedicated typists, later by programmers themselves.
• Teletypes, acoustic coupler modems, early ASCII terminals, line-oriented editors like ed, and control sequences like Ctrl‑U/W are mentioned as shaping terse Unix tooling.
• Long online sessions were rare early on due to phone costs; batch uploads/downloads were more typical.

Gender roles, labor markets, and feminism

• Several comments discuss how married women were often pushed or fired out of office/technical jobs mid‑20th century, leaving many skilled women underemployed.
• The company’s all‑female, home‑based model is framed as both exploiting and alleviating this exclusion, letting women combine paid work with domestic expectations.
• Participants debate historical labor-force statistics: some argue women already worked in large numbers but were concentrated in low‑status jobs; others stress rapid change from 1959 onward.
• Sexual harassment and limited job options after childbirth are mentioned as further barriers.

Skills, backgrounds, and difficulty of early programming

• Some assume many early women programmers had strong math/physics backgrounds; others counter that advanced math does not automatically translate into programming ability.
• There is debate over whether assembly is “easier” than higher mathematics; consensus within the thread is that assembly is conceptually simpler but demands detailed, memory‑intensive work.

Bias, names, and customer behavior

• An anecdote about two support workers accidentally swapping names suggests clients responded more positively to a male name and more confrontationally to a female name.
• Some accept this as illustrative of subtle sexism; others doubt the story’s realism and note that such hypotheses can be tested experimentally.
• Workplace data from one company allegedly showed female support agents receiving significantly more abuse than male colleagues.
• A separate incident where a conference used fake female speaker profiles leads to debate:
  • One side sees it as evidence of sexism and preference for controllable “sockpuppets.”
  • Another side frames it as gaming diversity quotas rather than disliking women per se.
  • There is disagreement over whether organizers truly “couldn’t find” real women speakers or merely couldn’t find women willing to deliver the messages they wanted.
• Quotas and “affirmative action culture” are criticized by some as creating perverse incentives, though others see them as a response to women’s underrepresentation and reluctance to speak.

Perceptions of women leaders

• Comments note that individual female political leaders can affect perceptions of women’s suitability for power.
• Examples from UK politics are used to argue that both success and failure by women in top roles can raise or lower the odds that male‑dominated establishments back future female leaders.

Company structure, profit-sharing, and ownership

• One commenter criticizes that only 70 out of 8,500 people reportedly became millionaires, questioning claims of “profit‑sharing and co‑ownership.”
• Others respond that:
  • The 8,500 figure reflects total employees over time, many part‑time or temporary.
  • Co‑ownership typically has vesting/earn‑in requirements.
  • In the historical context, giving any significant equity to non‑capital‑owning workers was unusual.
• Another commenter notes the founder was never described as running a cooperative; profit‑sharing need not mean equal shares.

Tapping underused talent pools

• The company’s success with married women working from home sparks discussion of other underutilized groups, such as laid‑off US manufacturing workers in small towns.
• Examples include an effort to apply surplus autoworker skills to solar infrastructure, and a historical analogy to the “putting‑out system,” where merchants distributed tools and raw materials to rural households to tap idle labor.

Miscellaneous details and resources

• The original company name was “Freelance Programmers,” later renamed several times before becoming part of a larger IT group.
• Her philanthropy included supporting premises for a London IT livery company.
• A 1979 video is linked, framing home programming as a major revolution for working women, and a podcast episode about her autobiography is shared.