The Late-Night Doubt Is Not a Signal to Stop
There is a version of me that shows up around 11:45pm and thinks the whole thing is stupid.
Every project. Every night. Same guy.
He is very persuasive. He has data. He points at the analytics tab. He points at the empty inbox. He points at the friend who didn't reply to my text about the launch. He says: see? nobody cares. go to bed.
For a while I thought that guy was telling me the truth. That the late-night version was the honest version, and the daytime version was the delusional one.
It's the other way around
The late-night guy is not honest. He is just tired. And tired has opinions.
Here is what I do now: when the 11:45 thought shows up, I write it down in the notes app and I close the laptop. I don't argue with it. I don't try to talk myself out of it. I just log it, like a weather report, and I go to bed.
In the morning, I re-read the note. Almost every single time, it reads like something a stranger wrote. Overheated. Certain. Not quite tracking with reality.
Why this matters
If you quit at 11:45pm, you are not making a real decision. You are letting a very specific chemistry make it for you.
Real decisions get made in daylight, with coffee, ideally after a walk. If the project still looks bad at 10am on a Tuesday — okay, maybe there's a real problem. But not at midnight. Never at midnight.
The rule I try to live by now: no permanent decisions after 10pm.
Especially not about the thing you love.
The 11:45pm log, one year in
I still have the notes. Reading them back is the most useful thing I have done for my own head, so here are four actual entries, unedited:
- "Nobody is going to pay for any of this. Stop."
- "You are 50. This is a hobby you are calling a business."
- "Six apps and zero dollars. Do the math."
- "Everyone can see you failing in public."
Every single one of those felt like a verdict at the time. Reading them in daylight, they are not analysis. They are the same four sentences on a loop, dressed up differently. Tired brain does not generate new information. It just recycles fear with more confidence.
How to tell doubt from data
This is the distinction that took me months. Both feel identical at midnight, so I use a test that has nothing to do with how convinced I feel:
- Doubt is about you. I am too old, too slow, too late, not smart enough. It has no next action attached. It arrives at night and leaves at breakfast.
- Data is about the thing. Three people tried the signup and none finished it. It is specific, it is checkable, and it survives the morning.
If the thought does not name a fact you could verify tomorrow, it is not information. It is weather.
The one time the late-night guy was right
I want to be honest, because "always ignore your doubt" is bad advice.
There was a project I kept pushing for weeks while the midnight voice said this one is not it. That time the voice was right — and I could tell in the morning too, because the daytime version agreed. The signal was not the intensity of the feeling. The signal was that it was still there at 9am, with reasons attached.
That is the whole rule. Doubt that survives daylight and comes with specifics deserves a real decision. Doubt that evaporates with coffee deserves a note and a closed laptop.
Keep reading
The Part Where You Feel Ridiculous
Fifty years old, no coding background, typing into a chat box like it owes me a business. Yeah, it feels ridiculous. Do it anyway.
Nobody Is Coming to Help You Build This
The quiet part of starting something new: there is no team, no cofounder in the next chair, no boss to escalate to. Just you and a blinking cursor.
The Support System I Wish I'd Had (And What I Did Instead)
No incubator. No accelerator. No slack channel of peers. Here's what I cobbled together instead — and honestly, it was enough.
Before You Build, Interrogate the Idea
You have an incredible AI research analyst on call. Use it before you spend three months building the wrong thing.