The APL timeline I wrote about last week opens on 1970, and its first live demo is A‘70: APL\360 as people typed it then.
Badges
Badges come from GitHub once the author claims this feed.
Recent posts
every link opens the author’s post-
TBT #15: APL\360 on an IBM 2741, Printing on Green-Bar Paper
-
Worth Reading #3: Design Patterns and Testing — the Gang of Four, Pree and Binder
The prior post in this series was about architecture and design.
-
Saw #19: Taking Inventory — agentrail, a Home Page, and a Week of X_eTaL
This Sunday’s saw changed twice while I wrote it.
-
TBT #14: APL, Forth and Lisp Timelines
Three languages I keep coming back to are APL, Forth and Lisp.
-
Worth Reading #2: Architecture and Design — Alexander and Rowe
The prior post in this series was about the people who write software.
-
Saw #18: Fine-Tuning, Manifolds, Ray Tracing, a Debugger, and More
Eight saws this week, all of them about later work: two new X_eTaL repositories, one for fine-tuning and one for manifolds; ray tracing in X_eTaL itself; animated terminals for my APL demos; clearer advice on applying a group; a debugger for X_eTaL, on the way to editors and…
-
Array Languages #20: A Ray Tracer in X_eTaL, on CPU and GPU
X_eTaL-gpu runs X_eTaL source on the GPU by lowering it through an intermediate form to OpenCL.
-
Dogfooding #3: CoSy Tests reva-fork — Bug Reports, Fixed or Filed
Saw #16 introduced reva-fork, my port of the Reva Forth to Rust and WebAssembly, and CoSy, an APL-like language, running on top of it.
-
Why I Use #8: fd, ripgrep, skim, dua and bat — Rust at the Prompt
The prior post was about getting to a prompt and keeping it.
-
Worth Reading #1: The People Who Write Software — Weinberg and Brooks
This series is a way to acknowledge, and share, what I have read that influenced my approach to software development, and much of that goes beyond coding.
-
Why I Use #7: iTerm2, autossh, tmux and Chrome Remote Desktop — From the MacBook to the Machines
The prior post in this series was about coding agents.
-
Why I Use #6: Coding Agents, and the Models Around Them
The prior post in this series was about GNU’s tools, which I have used for decades.
-
Dogfooding #2: A Chain of Tools, Each Testing the One Below
The first Dogfooding post was about one tool finding the limits of another: a Pascal VM’s allocator, outgrown by an OCaml written in Pascal.