
Abstraction
Leaving the visible world behind, on purpose.
- 51
- in technology
- 9:51
- average
- 502 min
- in total
- 407
- across the network


Chiplet

Relational model
Codd’s 1969 relational model is a formal specification—not software, not SQL, not a product. It defines data as tuples in relations, enforces consistency via logic, and insists all information be explicit. Real databases violate it daily. That gap is where data engineering begins.

Domain Name System
DNS is the distributed name-resolution system invented by Paul Mockapetris in 1983. It replaced the ARPAnet’s central hosts file. It uses a hierarchical zone model and originally ran over UDP. Later concerns about reliability, security, and privacy drove TCP use and protocol extensions. RFCs 882, 883, 973, 1034, and 1035 define its evolution. Mockapetris implemented the first version, 'Jeeves', for TOPS-20 the same year.

REST
REST is Roy Fielding’s 2000 architectural style for the Web. It defines constraints—not rules—to diagnose scalability failures in distributed hypermedia systems. Its power lies in exposing gaps between promise and practice, especially around statelessness and HATEOAS. Most so-called RESTful APIs ignore its core mechanism: hypermedia-driven state transitions.

Internet protocol suite
TCP/IP is a layered framework for end-to-end data communication. It specifies how data should be packetised, addressed, transmitted, routed, and received. Its architecture rests on the end-to-end principle—placing intelligence at the edges—and uses encapsulation and the robustness principle (conservative sending, liberal receiving) to achieve interoperability across heterogeneous networks. Developed by Cerf and Kahn starting in 1973 under DARPA, it replaced the ARPANET's NCP with a modular, host-responsible reliability model. IPv4 was installed in the ARPANET in 1983, and TCP/IP was formally adopted as the US DoD standard in March 1982. The defining technical specifications are RFC 1122 and RFC 1123, which codify its four-layer abstraction model.

Terraform (software)
Terraform is infrastructure-as-code software developed by HashiCorp in 2014. It uses declarative configuration (HCL or JSON) and provider plugins to manage infrastructure across clouds and on-prem systems. It shifted from MPL 2.0 to BUSL on 10 August 2023, restricting commercial use by competitors and prompting the OpenTofu fork. It supports automation in large-scale service-oriented development but requires strict state management and does not enforce security or runtime behaviour.

Metaverse

PDF delivers guaranteed visual consistency for static documents—but only by freezing layout, embedding everything, and avoiding runtime logic. Its shift to ISO control removed Adobe’s proprietary hooks, yet its security model remains brittle under active exploitation.

Unity (game engine)

AmigaOS

Arista Networks

ARM architecture family

ChromeOS

Cookie

CSS

Game engine

HTML

Kotlin

NeXTSTEP

Objective-C

Package manager

RAID

Redis
Redis is an in-memory key-value database introduced in 2009 by Salvatore Sanfilippo to solve scalability issues at his startup LLOOGG. It delivers low-latency operations by holding all data in memory and using the fork system call to enable concurrent client service and disk persistence. It supports two persistence methods—RDB snapshotting and AOF journaling—with journaling introduced in version 1.1 and considered safer. Default configuration limits data loss to a few seconds upon full system failure. Redis supports master-replica replication with hierarchical trees and introduced clustering in April 2015 with version 3.0. It grew into one of the world’s most popular databases for caching, message brokering, and primary storage. In December 2024, Sanfilippo returned to Redis and implemented the Vector Set data structure for vector similarity search.

System on a chip

Graphical user interface

Virtual machine

WebAssembly

Windows 95

Windows NT

ALGOL

Amazon Web Services

Advanced Message Queuing Protocol

C++
C++ is a systems programming language that enables high-level abstractions without runtime overhead. It delivers performance and control—but only to those who master its intricate, unforgiving rules.

C (programming language)
C is a deliberately minimal, hardware-close language that enabled Unix to become portable. It trades safety and abstraction for control and efficiency—and that trade still defines systems programming.

COBOL

Docker (software)

Fortran
Fortran is the first high-level programming language to achieve broad use. It succeeded not by abstracting away hardware, but by proving abstraction could coexist with assembly-level performance — specifically for numeric computation on the IBM 704. Its compiler introduced the basic block and Monte Carlo–driven memory layout, establishing techniques that remain standard. It made computing accessible to scientists — but only those doing number-crunching, and only on IBM hardware.

IBM System/360
The IBM System/360 established architectural compatibility as a design principle — not a marketing claim. It delivered real portability across a wide performance range using microcode and custom transistor packaging. Its limitations — no ICs, partial model incompatibility, rare max-memory deployments — are as instructive as its successes.

Java (programming language)
Java is a programming language built to enforce portability through mandatory compilation to JVM bytecode and strict memory safety via garbage collection and pointer omission. It solves cross-platform inconsistency at the cost of runtime overhead and abstraction rigidity. Its success rests on standardisation—not inevitability.

Kubernetes

Lisp (programming language)
Lisp is the first language to treat code as data—and the first to prove that a small set of primitives plus eval suffices for universal computation. Its cost is runtime overhead; its payoff is programmable programmability.

NVM Express

Pascal (programming language)
Pascal is a disciplined, small-language experiment from 1970. It delivers on teaching structured programming and safe data modelling. It fails as a general-purpose systems language. Its influence lies in its constraints — not its adoption.

Python (programming language)
Python is a dynamically typed, whitespace-delimited programming language conceived by Guido van Rossum in December 1989 as a successor to ABC. Its first release was Python 0.9.0 in 1991. It introduced a strict visual grammar for code blocks, paired dynamic typing with reference counting and cycle detection for memory management, and codified its philosophy in PEP 20. Python 3.0 (2008) broke backward compatibility. Optional static typing arrived in 3.5. Van Rossum named it after Monty Python's Flying Circus and wrote the first interpreter as a Christmas holiday project.

Ruby (programming language)
Ruby is a deliberately opinionated scripting language that enforces object uniformity at runtime. It delivers on its promise of simplicity and expressiveness—but only within its chosen domain: developer-facing tools and applications where flexibility trumps performance or safety.

SQL

TypeScript
TypeScript is a compiler-layered static typing system for JavaScript. It solves scalability problems in large codebases by enabling early error detection and better tooling — without breaking compatibility. Its mechanism is transpilation, not runtime enforcement. Its biggest win is developer velocity in complex projects — proven by the 8–12× speedup in TypeScript 7.0. Its cost is added complexity and no runtime guarantees.

VMware Workstation

XML
XML is a deliberately constrained application profile of SGML, standardised by W3C in 1998. It delivers strict, interoperable document structure at the cost of verbosity, parsing overhead, and zero runtime semantics. It succeeded where SGML failed—not by being simpler, but by being bounded.
