I set up a custom email domain in three minutes. In 2010 this took me a day.

In 2010 I set up a custom email domain for a small business. It took most of a day. I logged into the registrar, found the DNS settings, added MX records, waited, checked propagation, added SPF records, waited again, tested from a different account, discovered I'd made a typo, fixed it, waited more. The email eventually worked. I felt like I'd accomplished something real.

Last week I needed digest@fieldnotes-ai.com to send the morning digest. Not receive -- just send. I wanted a professional from address instead of onboarding@resend.dev.

It took three minutes.

What actually happened

I went to Resend, added fieldnotes-ai.com as a domain. Resend showed me three DNS records to add: a DKIM TXT record, an SPF TXT record, and an MX record. I went to GoDaddy, added the records, came back.

Domain verified. DNS verified. DKIM verified. SPF verified.

Three minutes. One cup of coffee hadn't finished brewing.

I didn't touch a terminal. I didn't look up what SPF stands for. I didn't wonder if I'd entered the record value correctly or wait 48 hours to find out. Resend auto-configured GoDaddy, verified everything in real time, and showed me green checkmarks.

What this actually means

In 2010, the complexity was real. DNS propagation genuinely took 24-48 hours. SPF records had to be hand-crafted. DKIM required generating key pairs and knowing where to put them. Email deliverability was something only specialists fully understood. If you got it wrong, your emails went to spam and you didn't always know why.

The knowledge hasn't disappeared. Resend still adds DKIM signatures, still configures SPF correctly, still handles the MX routing. All of that infrastructure exists and runs. It's just invisible now.

This is a pattern I keep running into. The thing that used to take a day now takes minutes -- not because the underlying problem got simpler, but because someone built a layer on top of it that handles the complexity for you.

Vercel did this for deployments. Supabase did it for databases. Resend did it for email. And Claude.ai is doing it for architecture and code.

The part that made me pause

After Resend verified my domain, I updated one environment variable -- RESEND_FROM_EMAIL=digest@fieldnotes-ai.com -- in three places: local .env.local, GitHub Actions secrets, and Vercel. That was literally the entire migration. The next email went out from the new address. No code changes. No redeployment. No waiting.

I showed this to a developer friend who's been in the industry for fifteen years. His reaction: "That's it?"

Yes. That's it.

The first digest email from digest@fieldnotes-ai.com landed in my inbox that evening. The sender looked legitimate. The DKIM signature was valid. Gmail showed no warnings.

In 2010, getting to that point would have been a small victory worth documenting. In 2026, it's barely worth a Field Note.

Except that the gap between those two sentences is the whole story.