Tag Archives: machine-readable

Many of today’s programmers—excuse me, software engineers—consider themselves “creatives.” Artists of a sort. They are given to ostentatious personal websites with cleverly hidden Easter eggs and parallax scrolling; they confer upon themselves multihyphenate job titles (“ex-Amazon-engineer-investor-author”) and crowd their laptops with identity-signaling vinyl stickers. Some regard themselves as literary sophisticates. …

I was entering the miseries of seventh grade in the fall of 1980 when a friend dragged me into a dimly lit second-floor room. The school had recently installed a newfangled Commodore PET computer, a squat and angular box that glowed in the corner. “You gotta try this,” he told …

In the beginning was the Word, and the Word was in plaintext, and the Word was in plaintext because plaintext was the Way. It was good. On the sixth day—I’m skipping ahead here—the internet was born. The Word needed to be rewritten in HTML. Now there were two Words. It …

In my first job out of college, I was assigned the task of rewriting the autocomplete feature of a search page. The original code, entombed in a decrepit codebase, was a nauseating monstrosity that others wanted no truck with. The plan was to rewrite it in TypeScript—a dialect of JavaScript—drawing …

The German historian Oswald Spengler considered our age the age of abstraction. Nowhere is this more apparent than in programming, where abstraction isn’t just a conceptual convenience but an absolute necessity. Programmers like to talk about their tools (rather abstractly) as a “stack.” At the top of the stack—the surface …

Lex Fridman has done many long interviews on his popular podcast. Even so, the episode with the legendary programmer John Carmack has an unhinged director’s-cut feel to it. Over five hours, Carmack dishes on everything from vector operations to Doom. But it’s something Fridman says, offhand, that really justifies the …