I'm 57 and I create real software with AI. Here's what nobody tells you.

It was a Tuesday, and I was sitting at my kitchen table in my robe, holding a cup of coffee I'd let go cold.

On the screen in front of me was a website. My website. The one for this newsletter.

The thing is, I hadn't built it the way I built websites in 1995. I hadn't written a single line of code. I'd just described what I wanted, out loud, like I was telling a contractor what I pictured for a kitchen remodel.

And there it was. Live. Working. Mine.

I sat there for a full minute in this strange, quiet disbelief. Not the fireworks kind. The kind where your chest goes tight and you think, wait, that actually worked?

Nobody warns you about that moment. They warn you about everything else. But not that one.

If you've ever felt like the AI train left the station without you, this newsletter is the one that comes back to get you. Subscribe, or just hit reply and tell me where you're stuck. I read every one.

First, the lie I believed for two years

For two solid years, people told me I should "try AI."

And every time, I heard the same thing underneath it: this is for the young people. The 25-year-olds in hoodies posting threads about "shipping." The bros.

I'm 57. I founded adoption.com back in 1995 (and sold it years ago). I taught school in Texas. I ran orphanages in Ethiopia, Kenya, and Haiti. I raised seven kids.

I have done genuinely hard things. And yet this one little thing, AI, made me feel like I'd missed the bell and the whole class had moved on without me.

Here's what nobody tells you: the feeling that you're too late is the single most common feeling among the people who are about to be excellent at this.

So let me tell you what it's actually like. The real thing. Not the highlight reel.

Truth #1: You don't write code. You describe what you want.

This is the part that breaks people's brains, so let me say it plainly.

When I work with Claude Code (that's the tool I use most, with my AI collaborator I call Charlie), I'm not typing computer language.

I'm typing English. Regular, kitchen-table English.

I say things like: "Make the headline bigger and warmer, and move the subscribe button up so people see it before they scroll."

And it does it. Then I say, "No, smaller. And softer pink." And it does that too.

You don't need to learn to speak computer. You need to get good at saying what you actually want. And honey, women our age have been doing that our whole lives.

That's the whole game. Describe, look, adjust. Describe, look, adjust.

Truth #2: You will feel like a fraud. The feeling is a liar.

Let me be honest about something.

The first few weeks, I felt like I was cheating. Like at any moment a real programmer was going to walk in, look over my shoulder, and say, "Ma'am, you don't actually know what you're doing."

That voice is the impostor talking. And the impostor lies.

Because here's the truth I had to learn the hard way: using a tool to build something real is not cheating. It's just building.

A contractor uses a nail gun. A chef uses a stand mixer. I described a research tool I needed, and Charlie and I built it together over an afternoon. None of us is a fraud. We all used the tool that was in front of us.

Know someone who keeps saying "I'd be no good at that"? Forward them this section. That sentence is the only thing standing between them and a thing they'd love.

Truth #3: Things break constantly. That's the middle, not the end.

Nobody shows you this part, so I will.

Most of building real things with AI looks like this: I ask for something. It half-works. The button's in the wrong spot. The page loads crooked on my phone. Something I fixed yesterday is broken again today.

In the hype videos, you describe an app and a finished product appears in a glittering ten-second montage.

In real life, you describe an app, and then you spend forty minutes going "no, not like that, like this," and slowly it becomes the thing you pictured.

The breaking isn't failure. The breaking IS the work. Every single person doing this, the 25-year-old in the hoodie included, lives in that messy middle. They just don't film it.

When something broke and I didn't quit, that's the day I actually became someone who builds things.

Truth #4: The real skill is one you already have

Here is the part I most want you to hear.

The hardest skill in all of this isn't technical. It's being clear about what you want.

You'd be amazed how many people freeze up not because they can't use the tool, but because they genuinely don't know what they're asking for. They can't describe the end result. They wave their hands.

Now think about who's actually good at saying exactly what they want, in plain words, under pressure.

• People who've run a business and had to brief a team
• People who've raised kids and explained the same thing nine different ways
• People who've managed contractors, vendors, volunteers, chaos
• People who've survived hard years and learned to name what they need

That's you. That's us.

The thing the young builders are still learning, you've been practicing for thirty years.

They call it "prompting." We just call it knowing your own mind.

Before vs. after (the honest version)

Before, my idea of "building something online" meant hiring someone, waiting weeks, and paying for changes one email at a time.

After, I describe it, I watch it appear, I adjust it myself, in real time, in my robe, with cold coffee.

Before, "I'm not techie" was a wall.

After, I found out the wall was never technical. It was permission. I just hadn't given myself any.

Who this is for

It's for Liz, the version of you who's smart and capable and has been told for three years she should "try AI" and hasn't, because it felt like one more thing she'd be bad at.

It's for anyone who built a life full of hard, real things and somehow decided this one was off-limits.

It was never off-limits. The barrier was never your age. It was never that you "aren't techie."

The barrier was permission. So here it is, from me to you: you're allowed. You're not too old. You never were.

Send this to someone over 50 who keeps saying "that ship has sailed for me." It hasn't. Tell them I said so.

Quick questions people actually ask

Can you really build software with AI without knowing how to code?
Yes. I built my newsletter website without writing a single line of code. You describe what you want in plain English, the AI builds it, and you adjust by talking to it. The skill is clear description, not programming.

Am I too old to learn to build things with AI?
No. The feeling that you're too late is the most common feeling among people who turn out to be great at this. Decades of running businesses, raising kids, and managing people are exactly the experience that makes AI useful, not a disadvantage.

What AI tool do you use to build software?
I use Claude Code most often, with an AI collaborator I call Charlie. I talk to it in ordinary English, look at what it makes, and refine it in real time. Other tools work the same way: describe, look, adjust.

I write every week about what I'm actually building with AI at 57, the wins, the things that break, and the stuff nobody else admits. No jargon. No bro energy. Just a peer showing her work. Subscribe below and come build something with me.