Skip to content

Atlas

Reference diagrams grounded in the course’s 68 dated events.

Technology Evolution Atlas overview

Six computing eras from 1940 to 2030 with the count of source-backed events in each band.

Six computing eras from 1940 to 2030, six teaching bands Two coordinated views. Top view: six era band cards stacked top-to-bottom from AI-scale systems E6 at the top down to Early computing E1 at the bottom, each carrying date range, defining shift and a source-backed anchor. Bottom view: a snake-laid succession chain of six cards (3 per row), each showing the single new capability that era added on top of the previous plus a source anchor. E6 emphasised in both views. SIX COMPUTING ERAS Source: Computer History Museum E6 AI-scale systems 2017-2030 Transformers, foundation models, platform scale and policy frameworks. Anchor: Vaswani et al. "Attention Is All You Need", 2017. E5 Cloud, mobile, and data 2005-2016 Elastic infrastructure, mobile-first, DevOps and machine learning at scale. Anchor: AWS S3 launch, March 2006; iPhone launch, June 2007. E4 Web and open standards 1990-2004 World Wide Web, open source movement, governance frameworks. Anchor: World Wide Web public release, August 1991. E3 Networked systems 1970-1989 Internetworking, Unix, relational databases, public-key cryptography. Anchor: TCP/IP transition on ARPANET, 1 January 1983. E2 Mainframe and time-sharing 1960-1969 Time-sharing moved computing beyond batch jobs. Anchor: CTSS at MIT, 1961; Multics, 1965. E1 Early computing 1940-1959 Stored-program theory, programmable hardware, magnetic core memory. Anchor: ENIAC, 1945; first stored-program machine, 1948. SUCCESSION - EACH ERA INHERITS AND ADDS E1 Compute ENIAC, 1945 E2 + Time-sharing CTSS, 1961 E3 + Networking ARPANET, 1969 E4 + Open web WWW, 1991 E5 + Cloud scale AWS S3, 2006 E6 + AI scale Transformer, 2017 adds adds then adds adds The arc: 68 dated atlas events across six bands Top view: era bands with anchor events. Bottom view: each era inherits the previous and adds one newcapability. E6 is the live present.

Era bands are teaching groupings, not single-cause boundaries. Source: Computer History Museum.

Domain lane timeline, 1940 to 2030

Nine domains across the same time axis. Solid dots are historical entries; hollow dots are forecast or future-dated entries.

Nine domain lanes, 1940 to 2030 timeline Nine horizontal lanes show networking, cybersecurity, AI and machine learning, software, standards, cloud, data, web and hardware. Each lane carries representative milestones with year and short label. Networking and AI lanes are emphasised in brand red. NINE DOMAIN LANES Source: Computer History Museum NETWORKING Networking 1969 ARPANET 1983 TCP/IP cutover 2015 HTTP/2 CYBERSECURITY Cybersecurity 1976 Public-key crypto 2001 AES standard 2017 WannaCry AI / ML AI and machine learning 1956 Dartmouth 1986 Backprop 2017 Transformer SOFTWARE Software engineering 1968 NATO conf 2001 Agile 2013 Docker STANDARDS Standards and governance 1947 ISO 1986 IETF 1994 W3C CLOUD Cloud infrastructure 2006 AWS S3 2014 Kubernetes DATA Data management 1970 Relational 2006 Hadoop 2014 DCAT WEB Web technologies 1991 WWW public 1999 Ajax era 2014 HTML5 HARDWARE Hardware 1947 Transistor 1971 Intel 4004 2007 iPhone 1940 1960 1980 2000 2020 Position carries chronology; lane carries domain Lanes in brand red mark the two domains the course pivots on (networking and AI). Other lanes use ink to keep the chronologyreadable.

Position carries chronology; lane carries domain. Source: Computer History Museum.

Standards Adoption Map

Institutions, internet base, language and data, platform interfaces.

Standards Adoption Map, tech evolution course visual Four chronological waves of standards adoption. Each column lists the period, the kind of artefact and the three named standards bodies or specifications that define the wave. STANDARDS ADOPTION MAP Source: IETF, W3C, ISO, IEEE Institutions, internet base, language and data, platform interfaces. W1 Institutions 1947-1986 Bodies that provide thevenue and the process. 1947 ISO founded, Geneva iso.org 1963 IEEE incorporated, USA ieee.org 1986 IETF first meeting ietf.org W2 Internet base 1983-1995 Naming, routing, and webgovernance mature. 1983 DNS specified, RFC882-883 datatracker.ietf.org 1989 BGP, RFC 1105 datatracker.ietf.org 1994 W3C founded, MIT w3.org W3 Language and data 1988-2006 Portable systems and commonformats scale reuse. 1988 POSIX.1 published ieee.org 1997 ECMAScript Edition 1 ecma-international.org 2006 JSON, RFC 4627 datatracker.ietf.org W4 Platform interfaces 2012-2017 APIs, authorisation, webruntime portability. 2012 OAuth 2.0, RFC 6749 datatracker.ietf.org 2015 OpenAPI 2.0 released openapis.org 2017 WebAssembly 1.0 inbrowsers w3.org 4 adoption waves, 12 dated artefacts The rightmost column (W4) is the present wave, emphasised in brand red. Arrows mark chronology, not direct causal claims.

Four chronological waves of standards adoption. Source: IETF, W3C, ISO, IEEE.

Security Controls and Failure Signals

Cryptographic base, internet exposure, systemic incidents, assurance models.

Security Controls and Failure Signals A security-focused chronology. Control cards name the standards and frameworks adopted in each wave. Incident cards name the failures that exposed gaps in those controls. SECURITY CONTROLS AND FAILURE SIGNALS Source: NIST CSRC, CERT, MITRE Cryptographic base, internet exposure, systemic incidents, assurance models. W1 Cryptographic base 1976-2001 Public standards andprimitives becomedeployable controls. 1976 Diffie-Hellman keyexchange ieee.org 1977 DES, FIPS 46 csrc.nist.gov 2001 AES, FIPS 197 csrc.nist.gov W2 Internet exposure 1988-2015 Networked systems makefailures and trust visible. 1988 Morris worm, CERTfounded cert.org 1999 TLS 1.0, RFC 2246 datatracker.ietf.org 2015 Let's Encrypt launches letsencrypt.org W3 Systemic incidents 2017-2020 Ransomware, mass dataexposure, supply-chaincompromise. 2017 WannaCry: 200,000systems ncsc.gov.uk 2017 Equifax breach: 147Mrecords ftc.gov 2020 SolarWinds Orioncompromise cisa.gov W4 Assurance models 2013-2022 Structured frameworks forgovernance and response. 2013 MITRE ATT&CK matrixreleased attack.mitre.org 2014 NIST CybersecurityFramework 1.0 csrc.nist.gov 2020 Zero Trust Architecture,SP 800-207 csrc.nist.gov 4 adoption waves, 12 dated artefacts The rightmost column (W4) is the present wave, emphasised in brand red. Arrows mark chronology, not direct causal claims.

A security-focused chronology. Source: NIST CSRC, CERT, MITRE.

AI Adoption Waves

Framing the field, rules and retrenchment, statistical and deep learning, generative scale.

AI Adoption Waves, tech evolution course visual Four research waves from conceptual tests to foundation models. The grouping distinguishes research programmes from simple invention claims and shows when each wave entered widespread deployment. AI ADOPTION WAVES Source: Stanford CS221, Turing Archive Framing the field, rules and retrenchment, statistical and deep learning, generative scale. W1 Framing the field 1950-1956 Questions, conferences, andlanguage for AI. 1950 Turing's imitation gamepaper turingarchive.org 1956 Dartmouth summerworkshop stanford.edu W2 Rules and retrenchment 1974-1993 Expert systems grow;funding cycles down. 1974 Lighthill report, firstAI winter aaai.org 1980 MYCIN expert systemreleased stanford.edu 1986 Backpropagationpopularised nature.com W3 Statistical and deeplearning 1995-2016 Margin methods, sequencemodels, embeddings, games. 1995 SVM published by Cortesand Vapnik springer.com 1997 LSTM by Hochreiter andSchmidhuber mit.edu 2012 AlexNet wins ImageNet image-net.org W4 Generative scale 2014-2022 Generative models andtransformer scaling. 2014 GANs by Goodfellow etal. arxiv.org/abs/1406.2661 2017 Transformer architecture arxiv.org/abs/1706.03762 2022 Diffusion models reachproduction arxiv.org 4 adoption waves, 11 dated artefacts The rightmost column (W4) is the present wave, emphasised in brand red. Arrows mark chronology, not direct causal claims.

Four research waves from conceptual tests to foundation models. Source: Stanford CS221, Turing Archive.

Software Delivery Waves

Process debate, shared code culture, web and cloud platform, operational packaging.

Software Delivery Waves, tech evolution course visual A software-engineering chronology. Columns mark when each delivery practice became mainstream, from waterfall lifecycle to containers and microservices. SOFTWARE DELIVERY WAVES Source: Bass, Clements, Kazman; 12factor.net Process debate, shared code culture, web and cloud platform, operational packaging. W1 Process debate 1970-2002 Planned lifecycle modelsmeet iterative practice. 1970 Royce's waterfall paper ieee.org 2001 Agile Manifesto,Snowbird agilemanifesto.org 2002 Test-driven developmentcodified martinfowler.com W2 Shared code culture 1991-2005 Reusable patterns, opensource, distributedhistory. 1991 Linux 0.01 by Torvalds kernel.org 1994 Design Patterns, Gang ofFour addison-wesley.com 2005 Git released by Torvalds git-scm.com W3 Web and cloud platform 2000-2014 Web architecture andelastic infrastructure. 2000 REST dissertation byFielding ics.uci.edu 2006 AWS S3 and EC2 launch aws.amazon.com 2009 DevOps coined, Velocityconf oreilly.com W4 Operational packaging 2013-2014 Containers, orchestration,service boundaries. 2013 Docker open-sourced docker.com 2014 Kubernetes 1.0 announced kubernetes.io 2014 Microservices article,Fowler martinfowler.com 4 adoption waves, 12 dated artefacts The rightmost column (W4) is the present wave, emphasised in brand red. Arrows mark chronology, not direct causal claims.

A software-engineering chronology. Source: Bass, Clements, Kazman; 12factor.net.