💻Culture & Status

Software Engineer · Writes, tests and maintains the code that runs modern life — and is one of the first professions watching AI automate its own daily work.

How society sees the software engineer has swung between clerical and glamorous more than once. Early programming was coded, quite literally, as women's work — detail-oriented and low-status, like typing — before the same job was rebranded as a high-status, world-changing pursuit once the money and power involved became obvious.

That whiplash still shows up in the culture: hacker mythology and Silicon Valley wealth on one side, basement-dwelling IT-support comedy on the other, and a real, well-documented drop in the share of women in the field since the 1980s in between.

Social standing through history

How much status the profession carried in each era, on a 0–100 scale.

3545608268
1950s–1960s1970s1980s–1990s2000s–2010s2020s
1950s–1960s

Programming was widely seen as clerical support work, comparable to typing, and was disproportionately staffed by women for exactly that reason; a widely read 1967 magazine article pitched it as a career suited to people who were good at planning a dinner party.

1970s

The 'software crisis' narrative around the 1968 NATO conference made clear how expensive and difficult good programming actually was, slowly raising the field's standing among engineers and managers even as pay stayed modest outside a few specialist firms.

1980s–1990s

Personal computing created its first celebrity engineers and self-made millionaires — Gates, Jobs, Wozniak — and hacker culture gained a countercultural cool, even as the broader public image stayed closer to the socially awkward nerd stereotype.

2000s–2010s

Google, Facebook and their peers made 'software engineer' one of the most sought-after graduate jobs in the world, with campuses designed to be aspirational workplaces and stock compensation that created real wealth well below the executive level.

2020s

Status has cooled from its peak: repeated rounds of layoffs at major technology companies, a tougher entry-level hiring market, and public skepticism about the industry's social effects have all landed on a profession that spent the 2010s feeling untouchable.

In film, books and art

Film2010

The Social Network

David Fincher (director); Aaron Sorkin (screenplay)

Dramatizes the founding of Facebook and the lawsuits that followed; less about code than about the ambition and betrayal of the people who write it, but hugely influential in shaping the public image of the founder-engineer.

TV series2014

Silicon Valley

Mike Judge

A satirical HBO comedy about a startup building a compression algorithm, mocking pitch decks, brogrammer culture and big-tech excess with enough specificity that many engineers treated it as a documentary.

TV series2006

The IT Crowd

Graham Linehan

A British sitcom set in a fictional company's basement IT department, built around the gap between how technical staff see themselves and how the rest of the office treats them.

TV series2014

Halt and Catch Fire

Christopher Cantwell and Christopher C. Rogers

A drama following hardware and software engineers through the PC clone wars, the online-services era and the early web, praised by many working engineers for how accurately it renders the feel of the work.

Film2016

Hidden Figures

Theodore Melfi (director)

Follows Black women mathematicians at NASA, including Dorothy Vaughan teaching herself and her team FORTRAN to keep their jobs as the agency installs an IBM mainframe — a direct dramatization of the human-computer-to-programmer transition.

Film2014

Who Am I – No System Is Safe

Baran bo Odar (director)

A German thriller about a young hacker collective, built around genuinely researched hacking and social-engineering techniques rather than Hollywood's usual fictional interfaces.

Proverbs and idioms

Garbage in, garbage out

US computing slang, 1950sA program is only as good as the data fed into it — no amount of clever code fixes bad input.

It's not a bug, it's a feature

Programmer folklore, since the 1970sA sardonic way of defending an unintended behavior as though it were intentional, rather than admitting a mistake.

Premature optimization is the root of all evil

Donald Knuth, 1974, attributed by him to C.A.R. HoareDon't spend time speeding up code before profiling proves where the real bottleneck is.

Talk is cheap. Show me the code.

Linus Torvalds, Linux kernel mailing list, 2000A working implementation settles an argument that discussion alone cannot.

Rites, symbols and dress

The technical interview

A live or virtual session solving algorithm problems on a whiteboard or shared document under time pressure — a genuine rite of passage into the profession that most working engineers have opinions about and few defend as pleasant.

The hackathon

A team builds a working prototype in a single overnight or 48-hour push, fueled by free food and branded T-shirts, then demos it to judges; equal parts bonding ritual, recruiting tool and genuine occasion for fast, scrappy learning.

Carrying the pager

Being added to a service's on-call rotation — literally a pager in the 1990s, now a phone app that can wake someone at 3 a.m. — marks the moment a company trusts an engineer with a production system's failures, not just its features.

None of this settles whether software engineering is really 'engineering' in the old sense, a craft, or something new that borrowed the name for credibility. The field itself has never fully agreed, and the argument shows up again in the debate over its own legends.

What has changed least is the gap between the job's image and its daily reality: neither the lone hacker genius nor the buttoned-up engineer in a hard hat looks much like a person reading a stack trace at 11 p.m., which is where most of the actual work happens.

Keep exploring

More in Engineering & Technology