dierker.us · est. 1996
Migration log · entry 015 · October 2026

Fifty years in.

Before this log gets consumed by launch season, a step back. I’ve been programming for almost fifty years. This migration is the biggest thing I’ve ever built, and I’m building it in a way that would have been science fiction for forty-eight of those years. Here’s the arc — and what it taught me about what actually changed.

It started on a TRS-80 — the “Trash-80,” we called it, with the affection you reserve for a thing that changes your life while deserving the nickname. BASIC first, COBOL in the same era. There was no Stack Overflow, no documentation beyond what shipped in the box, and no one to ask. You read, you typed, you broke it, you figured out why. That apprenticeship — the machine as your only teacher — turns out to have been the most durable education I ever got.

Timeline: late 1970s TRS-80 and BASIC/COBOL, 1994 first paid web work, 1996 server-side ASP, building CMS and ERP systems before those names existed, the PHP/Java/Python decades, the decade inheriting the supplier’s systems, and today’s AI-partnered migration late ’70s A TRS-80 and a manual BASIC, then COBOL — the machine as the only teacher 1994 First paid dev work a hand-built HTML website, when that was a profession-in-waiting 1996 Server-side: ASP pages that thought before they rendered ’90s–’00s Building things before their names content management before “CMS,” rudimentary ERPs before that was a thing the long middle PHP, Java, Python every paradigm the industry produced, learned on the job the last decade Inheriting the systems a decade operating them — then the decision to replace them, as architect now The migration, AI-partnered, in public fifteen entries and counting
Fifty years, seven stops. The gaps between dots hold most of the work.

The first paycheck for code came in 1994, for a hand-built HTML website, back when that sentence would have required explaining twice. By 1996 I was writing server-side pages in ASP — pages that thought before they rendered — and from there the pattern that defined my working life set in: building things before the industry had names for them. I was developing content management systems before anyone said “CMS.” I built rudimentary ERPs before that acronym meant anything to the businesses running them. Not because I was visionary — because a business had a problem, the problem had a shape, and the shape wanted software. Years later the industry would productize the shape and give it a name, and I’d learn I had been doing a thing. (Somewhere in there I collected a Microsoft certification, which I mention for completeness: it never once mattered.)

Then PHP, Java, Python — the long middle, where languages came and went but the job stayed the same. And eventually the chapter regular readers know from entry 1: a decade operating an industrial supplier’s inherited systems, learning every quirk of a decades-old stack, and finally the decision this log exists to document — replace it all, this time as the architect.

So, from the far end of fifty years: what’s actually different now?

The honest answer is the thing drafting this sentence. AI removed the barriers — effectively all of them. Not slowly, the way each previous wave did — compilers removed one barrier, open source another, Stack Overflow another — but wholesale. There is no syntax I have to hold in my head anymore, no framework whose conventions take a winter to absorb, no API whose documentation I have to spelunk alone the way I spelunked that TRS-80 manual. The distance between knowing what should exist and having it exist has collapsed to roughly the time it takes to describe it precisely. Readers of this log have watched that distance collapse in real time, entry after entry.

And what hasn’t changed? The two things that were scarce in 1977 and are exactly as scarce today. Raw talent — the knack for how computers think, which no tool has ever manufactured in someone who lacked it. And the ability to see a project in its completed state at inception — to stand in front of a half-million-SKU catalog on a dying ERP and already see the finished store: the search, the pricing engine, the portal, the sync keeping two systems honest. AI builds toward a vision at astonishing speed. It has never once supplied the vision. Every entry in this log started as something I could already see; the machinery just closed the gap faster than any decade of my career would have believed.

One more thing, since this is the personal entry and I may not write another. I’ve always understood computers — the languages, the logic, the way they think. It came easily when very little else did; I never understood humans half as well. There’s an irony I don’t know what to do with, fifty years in: the tool that finally removed every barrier between me and the machines is a computer that talks like a human. Maybe that’s the real story of this half-century — the machines and I kept meeting each other halfway, and they crossed the bigger distance.

Back to the build on Thursday. The migration is nearly ready to launch; the guy building it has been ready for fifty years.

← All entries