hn.today

A Family Tree of Software Job Titles

zwischenzugs.com456 points219 comments
Screenshot of A Family Tree of Software Job Titles

A historical map traces 104 software job titles from “Computer,” meaning a person who performed calculations, to the recent “AI Agent / Context Engineer.” Titles are arranged in five-year time bands and seven families, including development, operations, data and AI, security, testing, and customer support. Arrows distinguish direct descent from looser influence or common career moves; users can explore individual families and titles. The underlying chart is built from editable Graphviz and JSON files. Its dates indicate when titles became common, not their first appearance, and are explicitly estimates rather than fully researched citations.

The map highlights recurring patterns in how technology work is named and organised. Coding began as lower-status clerical translation of mathematicians’ plans, but later became creative programming - a history that complicates claims that AI will make coding unimportant. Roles also split and recombine: the generalist webmaster gave way to separate web, server, and content jobs, while front-end and back-end later reunited as full-stack development. Some titles fade or get absorbed, such as prompt engineer and scrum master; others are reused for unrelated work, as with systems engineer. New labels can revive old functions: today’s forward deployed engineers resemble earlier customer-embedded systems engineers. The enduring DevOps divide likewise persists through changing names: SRE and DevOps influence platform engineering, but the underlying tension between development and operations remains unresolved.

Read on zwischenzugs.com219 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Programming

Aristotle Expands into Rust

Aristotle has expanded its formal verification platform to Rust, allowing developers to prove code meets specifications and contains no undefined behavior, including in unsafe blocks. It can also verify that Rust rewrites behave like their original C code, targeting critical software such as smart contracts and infrastructure. (harmonic.fun)

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.