From Machine Code to AI: the Same Hello World

August 1, 2026 · ~1,650 words · 8 abstraction bands · 24 runnable variants · reading this as an AI agent? agents.md is for you

The interesting part is not that each layer can print Hello, World! - it is how the source is written at that layer, and what the layer hides. Scan one signature language from each band in a single row (Fig. 1), then zoom any pair in the compare panel (Fig. 2). Running is optional verification on this host (Linux x86_64), not the main event. Source panels use highlight.js 11.11.1 (same family as The Animation Is a Replay).

I have been learning ARM64 Assembly on an Apple Silicon Mac in a private teach-skill workspace. This public ladder walks the same idea from absolute machine words (and a period-style sum job) through early high-level languages (FORTRAN, Lisp, COBOL), systems and managed languages, scripting, and AI Engineering (tight contract vs casual vibe). Within a multi-language band, use the side-by-side arrows or the keyboard after you focus a rung. Assembly here is x86_64 Linux GAS, not the macOS ARM64 dialect from the private course.

Checking runner…

What each level hides (and when it showed up)

Robert C. Martin (Uncle Bob) has long treated programming history as a climb through successive languages and tools - machine code, assembly, high-level languages, and whatever comes next - and has argued in parallel that professionalism and craft still matter no matter how high the stack gets. That historical ladder is the spine of his 2016 talk The Future of Programming; the craft claim is the throughline of The Clean Coder (2011) and the software-craftsmanship talks that followed. A more recent long-form framing is his conversation with Kent Dodds (2025). The sentence above is a paraphrase of those themes, not a single slogan he trademarked. Bands on this page are ordered by abstraction, not pure release-year purity (Lisp is older than C; Java sits between C and Go). Years on each variant are introduction years, not "first Hello World ever printed."

• Absolute machine program (c. 1945) - instruction and data words entered into hardware. ENIAC (first run Dec 1945) was plugboards and ~3,000 switches, not a stored-program text file. Carousel: Hello via syscalls for ladder continuity, a sum 1..10 job for period honesty, and a modern ELF packaging note.
• Machine code (c. 1940s) - numeric encodings on front-panel switches, hex/octal, paper tape, or punched cards - without rewiring the whole machine per problem. Carousel: Hand-entered hex and Punch cards (sim) (80-col teaching sheet, not a live reader).
• Assembly (c. 1949) - mnemonics for those encodings. EDSAC (May 1949) and its "initial orders" are the classic early assembler story; its first jobs were tables of numbers, not greetings.
• Early high-level (1957–1959) - FORTRAN, Lisp, COBOL: formulas, lists, business data.
• Systems (1970–1985) - Pascal, C, C++ (PascalCase comes from Pascal).
• Managed / safe systems (1995–2015) - Java, C#, Go, Rust, Lean.
• Scripting / dynamic (1987–1995) - Bash, Perl, Python, PHP, JavaScript.
• AI Engineering (c. 2022–2025) - code behind a model interface; carousel peers are a tight prompt contract and a casual vibe one-liner.

Before FORTRAN and COBOL, people still wrote real programs - just not in those languages, and not by authoring an ELF file. Jobs were numerical tables, ballistics, census-style tabulation, payroll, and short loops (load / add / store / branch). Two different things are easy to conflate:

• Capability - a stored-program machine with character or teletype output (EDSAC-class, late 1940s onward) could already print any string, including the letters of "Hello, World," if someone encoded them. Nobody treated that as the first-program ritual yet.
• Convention - the cultural demo arrives later. Similar greeting examples show up around BCPL (Martin Richards, ~1967). The oldest surviving, well-dated written form is Brian Kernighan's 1972 B tutorial (hello, world via putchar). Kernighan & Ritchie's 1978 The C Programming Language is what made the phrase universal - it popularized the convention more than it invented the idea.

That is why the earliest carousel is not a fake 1945 greeting. The absolute band offers a minimal Hello via raw syscalls only so the ladder has a continuous thread, and next to it a more honest period job: sum 1..10 and print SUM=55. The sum is not filler; it is the historically better artifact for that band. ELF is only a packaging footnote - the OS shipping crate, not the handwritten invoice. We cannot put a 1949 console in your browser; Run still executes a real Linux binary - we do not make you toggle twenty-three switches.

Fig. 0 · IBM-style punch card (80 columns)

A classic blue 80-column punch card - source and data decks lived on paper like this, one character per column, holes for the encoding. The Machine code band's Punch cards (sim) slide is a teaching sheet for that form, not a live card reader. Photo: public domain (Wikimedia Commons; original by Gwern, horizontal crop by ArnoldReinhold). Source on Wikimedia Commons.

Fig. 3 · Eight bands - read the source, optionally run

Each band shows source first. Open Run on this host only if you want a live check: Run once (×1) or Run Program (×10) posts to /blog/from-machine-code-to-ai-the-same-hello-world/api/run/{language}?samples=N. Multi-language bands: ‹ › sit together; after you click a rung, arrow keys move within that band. Full sources: programs/ · runner server/app.py · page index.html.

Loading host hardware…

What you should notice when you read the sources

• Source shape first - Fig. 1 shows one signature per level in a single row; Fig. 2 zooms any pair (C next to Python, FORTRAN next to COBOL, absolute words next to Assembly). The syntax is the lesson.
• stdout mostly converges - later variants print the greeting; the absolute sum slide prints SUM=55 on purpose. Deltas are wall time, toolchains, years, and dumps (ELF / objdump).
• Capability vs convention - early bands could print characters long before anyone made "Hello, World" the first-program ritual (BCPL ~1967, B tutorial 1972, K&R 1978).
• Carousel bands - Early high-level, systems, managed, and scripting pack peers on one rung; years label each language.
• 1950s high-level is not "toy" - FORTRAN, Lisp, and COBOL still compile and run here via gfortran, SBCL, and GnuCOBOL.
• C is a hinge - short source, native binary, still close enough that compiler output looks like Assembly.
• AI Engineering is one layer, two styles - tight contract and vibe coding share L7 (same live GPT-5.6 Luna path). Tight uses a precise prompt; vibe is make a hello world. Cost appears in the Output panel and on the dashboard.

Quiz · don't leave until one answer sticks

What's still open

The private ARM64 teach path and this public x86_64 ladder are deliberately different ISAs - good for honesty, awkward for copy-paste between Mac and server. A dual-target Assembly pair (Apple Silicon vs Linux amd64) would make the platform gap visceral. AI and vibe rungs call GPT-5.6 Luna with per-request cost reporting, a cumulative ledger, and an email if spend exceeds $5. highlight.js is loaded modularly from esm.sh - if that CDN is blocked, sources stay readable as plain text.

Sources

For AI agents: the machine-oriented version is at agents.md, with directives, the allowlist contract, verified endpoints, an operational checklist, and a self-test.