technologybriefs
9:44in productionCh. 1 · From theory to terminal/ 9:44 · ceiling 15 min
Software · Systems

SQL

1974

SQL didn’t invent relational databases—it weaponised Codd’s model by making it usable.

SQL is the foundational query language for relational databases. It emerged from IBM’s System R project in the early 1970s as a usable alternative to the unreadable SQUARE notation. Developed by Chamberlin and Boyce after studying Codd’s relational model, it introduced set-oriented operations and access-path abstraction—two functional advantages over older APIs like ISAM. Validated through customer testing, it powered IBM’s commercial products (SQL/DS in 1981, Db2 in 1983) and preceded them in the market with Oracle V2 in 1979. It was among the first commercial languages to implement Codd’s model. It does not manage transactions, concurrency, or physical optimisation—those remain engine responsibilities. Its durability stems from its narrow, precise scope: describe data, not how to fetch it.

SoftwareSystemsAbstractionComputingDronesAbstraction across the network →
Chapters & takeaways4
  1. 1:03
    From theory to terminal

    SQL was the first widely adopted language to translate Codd’s theory into commercial practice.

  2. 2:41
    Why SQUARE failed

    SEQUEL succeeded because it replaced unreadable notation with plain-English syntax.

  3. 4:02
    The two abstractions

    Two functional wins: one command for many records, no need to specify how to reach them.

  4. 5:27
    Proven before productised

    Customer testing validated it; Oracle V2 shipped before IBM’s own commercial products.

Worth your time?

Yes. Study the whole thing.

4.5/ 5
What works
  • set-based querying
  • access-path abstraction
  • cross-vendor portability
What does not
  • enforce referential integrity
  • manage concurrent writes
  • define physical storage
Study it if
  • data engineers
  • analysts
  • backend developers
Skip it if
  • embedded systems programmers
  • real-time control engineers
The written brief1 min read

What it is and the problem it solves

SQL is a domain-specific language for querying and manipulating relational databases. It solves the problem of ad-hoc, human-readable data access without requiring knowledge of physical storage paths.

How it works

SQL uses declarative English-like syntax to specify what data to retrieve or manipulate, not how to access it. It operates on sets of records in a relational database, abstracting away physical storage details like indexes or file structures.

What works

Set-oriented record access works: one SELECT statement retrieves many rows. Access-path abstraction works: users do not specify indexes, pointers, or sequential scans—just logical conditions.

What does not

SQL does not enforce data integrity by itself. It does not handle concurrency control, transaction logging, or distributed consistency—those are implemented separately by database engines.

What it changes

SQL shifted database interaction from procedural navigation (move to record, read, move again) to set-based logic (select all matching rows). It made data access independent of storage layout and enabled non-programmers to write queries.

Is it worth your time

Yes—if you work with structured data, SQL remains the lowest-cost, most portable way to query across decades of systems. Its abstraction layer is still the baseline for all modern data interfaces.

Same field · Software4 of 114
10:46
Neo4jNeo4j Inc. · 2010Neo4j is a graph database built for relationship-heavy workloads. It delivers expressive querying and transactional safety—but horizontal scaling, vector search, and unified standards arrived over a decade after launch. Its value is real, but bounded by what it ships—not what it promises.
9:26
Unreal Engine1996Unreal Engine 1 is a historically specific implementation — not a general-purpose engine, not a platform, not open-source at launch, and not portable beyond late-1990s Windows PCs. Its value is archival, not functional.
9:38
Unity (game engine)2005Unity is a real-time 3D development platform first released in June 2005 for Mac OS X. It solves the problem of fragmented tooling by unifying authoring, rendering, physics, animation, and deployment into one editor. It abstracts platform-specific graphics APIs (DirectX, OpenGL, Vulkan) and input systems so the same code runs across Mac OS X, Windows, Linux, mobile, consoles, AR, and VR. Its cross-platform build system works reliably for iOS, Android, Windows, and macOS. Mecanim (introduced in Unity 4.0, November 2012) delivers robust, layered animation state machines. The Scriptable Render Pipeline (evolved from Unity 2018 onward) enables custom rendering paths like URP and HDRP. Unity does not deliver consistent performance across all target platforms without significant tuning. Its visual scripting tools remain secondary to C#. The 2023–2024 runtime fee proposal exposed fragility in its commercial model, even after cancellation. Unity changed who can ship polished interactive 3D software: indie teams, architects, educators, and automotive designers now ship production-grade visuals without building engines from scratch. It shifted real-time 3D development from specialist studios to generalist coders. Yes—if you need rapid iteration on small-to-mid-sized 3D or 2D projects across many platforms, and can absorb subscription licensing and runtime uncertainty. No—if you require full engine control, long-term perpetual licensing, or predictable deployment costs.
10:18
SmalltalkAlan Kay and team · 1972Smalltalk is a pure object-oriented language built for constructionist learning at Xerox PARC in the 1970s. Its first interpreter, Smalltalk-72, was written by Dan Ingalls in about 700 lines of BASIC for the Data General Nova in October 1972. It emerged from Alan Kay’s September 1972 bet that a message-passing core could fit on a page of code—and did so by the eighth morning. Smalltalk-80, released publicly in 1980, introduced foundational OOP ideas, featured an integrated development environment from inception, and established total reflection—both structural and computational. It has no primitive types: all values are objects, and all computation occurs via message passing. ANSI Smalltalk was ratified in 1998.
Up next in Technology

SSH File Transfer Protocol

Tatu Ylonen · 9:42

SFTP doesn’t secure your files—it assumes they’re already secure.

Play nextBack to Software
9:42