TL;DR: The fear that you missed the window assumes the window closed. It’s still open. AI moves fast, but the skill that matters isn’t memorizing this month’s tool. It’s the judgment to use any tool well, and that judgment compounds from wherever you start. Authors who feel hopelessly behind are usually one honest week of effort from competent. Here’s how I help non-tech authors use AI. The window isn’t last year.
It’s this week, and starting today puts you on the same curve as everyone else who’s going to matter in a few years.
The feeling of having missed it
Everyone else seems years ahead. They talk about tools you haven’t heard of, in shorthand you don’t speak, and the gap looks too wide to close. The conferences are full of people demoing workflows that read like science fiction to you. The articles assume you already know what a context window is and what an agent does. So you tell yourself the moment to get on board already passed, and you settle in to be left behind. That feeling is real. The conclusion under it is wrong.
Look closely at what makes someone seem ahead of you, and most of it is tool familiarity.Share on X
Let me walk through why, because the math of catching up on AI is different from the math of catching up on most other technical fields. The skill that decides whether you stay relevant isn’t the one that looks scariest to outsiders. It’s the one that compounds from any starting line. That means the catch-up problem is much smaller than it feels.
What does being behind on AI measure?
Look closely at what makes someone seem ahead of you, and most of it is tool familiarity. They know which buttons to press in this season’s app. That sounds like a lead until you remember the apps turn over every few months. The specific tool everyone is fluent in today will be replaced before you could have caught up to it anyway. Last spring’s hot model is this fall’s deprecated one. The workflow that won conference talks twelve months ago is the workflow nobody bothers to mention now, because there’s a better one.
That chase is a treadmill, and falling off the treadmill isn’t the same as losing the race. The people who look like they have a permanent lead mostly restart that lead every six months, along with everyone else. They have simply gotten louder about doing it. None of that is a moat. None of it compounds. A year of obsessive tool-chasing produces a person who knows last year’s tools well and is starting from scratch on this year’s, alongside the person who started this year cold.
Which skill does not expire in the AI era?
From the podcast
Martin Ricketts, thirty years into predicting technology trends, says the thing that transfers isn’t the tool, on Leaders and Their Stories:
Being good at prompt engineering is way more important than jumping around to every different tool.Which means the person starting today is behind on tools and even on the skill that outlasts them.
Underneath the tools sits the thing that actually matters, and it doesn’t reset every six months. The ability to ask a sharp question. The instinct to check the machine instead of trusting it, the judgment to know when an answer is confidently wrong and the discipline to verify it before publishing. Those skills carry from one tool to the next, and they compound. A person who builds them starting today passes the person who only memorized last year’s buttons, usually faster than either of them expects.
This is the part the tool tutorials skip over, because it’s harder to monetize than a course on the latest app. But it’s the entire game. The professionals who actually get useful work out of AI, the ones whose output is worth shipping, aren’t the people who know every feature. They’re the people who know when the machine is lying, when its output needs a complete rewrite, and when to throw away the draft and start over.
That’s judgment, and judgment is built one careful interaction at a time. The hallucination survival guide walks through the verification habits that matter most, and those habits are the same regardless of which model you’re using.
Why this week is the window
The window was never a fixed date you either made or missed. It opens the moment you start, because the judgment compounds from your first hour, not from some hour two years ago you cannot get back. If you start today, you’re not permanently behind the people who started earlier. You land on the same curve they’re on, gaining the part that lasts while the part they memorized expires around them.
The further back you trace this, the clearer it gets. People who were hopelessly behind on AI in 2023 and started seriously in 2024 are now ahead of the people who chased tools obsessively in 2022 and burned out before the foundation skills set in. The pattern repeats every twelve to eighteen months, and there’s no reason to believe the next cycle breaks it. Start this week and the same dynamic works in your favor.
Delay another year and you’ll be writing this same paragraph in twelve months, asking again whether it’s too late and getting the same answer.
What to actually do
You don’t need a course or a certificate. Take one real task you already do, a chunk of research, a messy set of notes, a rough outline, and run it through a tool this week. Watch where it helps and where it lies. Check its work by hand. Notice what you’d to fix and what was useful. That single honest hour teaches you more than a month of reading about the future, and it moves you from “hopelessly behind” to “started” in an afternoon.
Started is the only status that matters, because every later improvement compounds from there.
If your specific worry is the book you’ve been putting off because the AI question feels too overwhelming to face first, the answer is the same. Start the book the same way: take one real chunk of material you already have, run it through whatever tool you have access to, see what happens, fix what’s wrong. The act of doing that resolves the AI question into something concrete and workable, instead of a vague cloud of inadequacy.
The cornerstone piece on whether AI can write your book covers the line between what to delegate and what to keep, and that line is where the actual work starts.