Emotional Whiplash Is a Feature, Not a Bug
I have never been on a roller coaster that had the emotional range of a Tuesday spent building software.
One minute you're staring at a working feature you made — you, the person who can barely change the font in a Word document — and you feel like you've cracked open a small piece of the future. The next minute a single missing bracket has taken down your entire homepage and you're seriously considering a career change to something calmer, like air traffic control.
The peaks
Let me tell you about the peaks, because they're real and nobody warns you about them either.
The first time your app does the thing you asked it to do — actually does it, in front of you, in a browser — is a specific kind of joy. It's the joy of watching something you imagined become something you can click. There is nothing else in adult life that feels like it. The closest thing I can compare it to is the first time your kid rides a bike without you holding on.
That feeling comes back, in smaller doses, every single time something works. It never fully wears off. That's the fuel.
The valleys
The valleys are just as vivid.
- The bug that eats a whole afternoon and turns out to be a typo
- The moment you realize your "small change" broke three things you weren't looking at
- The stretch where you can't tell if you're actually making progress or just moving furniture around
- Sending your best work to a friend and getting a thumbs-up emoji
Each one of those, in isolation, is survivable. Stacked, they can make you want to quit before dinner.
The unnerving thing about the range
What surprised me isn't that there are highs and lows. It's how close together they are. Within a single 90-minute session, I have gone from "I am a genius, this is amazing" to "I have wasted my entire life" and back to "actually, this is kind of beautiful" — with no external input other than the AI politely giving me three wrong answers in a row.
If a human being talked to you the way your own inner monologue talks to you during a build session, you would end the friendship.
What the roller coaster is trying to tell you
Here's what I've come to believe: the emotional volatility is directly proportional to how much of yourself you're putting into the thing.
Boring project? Flat emotional line. Coasting.
Something you actually care about? All-caps highs, all-caps lows.
So when the ride gets rough, it's worth remembering: this only feels this intense because it matters. The alternative is to build something you don't care about, which would be smoother, but why would you do that.
Managing the ride without falling off
A few things that have helped me:
End sessions on a small win. Even if you're mid-bug, find something tiny you can finish — rename a button, tidy a paragraph, close a tab. Don't stop on defeat. Your brain will chew on the defeat all night.
Keep a "what worked" list. I have a running note where I write down every feature that works. On the bad days, I open it. It's ridiculous how quickly you forget what you've already built.
Don't build tired. I have never, ever made a good decision about my project after 10pm. Every "I'll just fix one more thing" past that hour has cost me hours the next day.
Zoom out on a schedule. Once a week, look at what the whole project actually is. In the daily grind you can't see it. From ten thousand feet it looks a lot better than it does from the trenches.
Tell someone the wins. Not the whole idea. Not the pitch. Just: "hey, I figured out the login flow tonight." Small victories, said out loud, become real.
The takeaway
You are going to be amazed at what you can create. And you are going to be surprised by how thoroughly the process can gut-punch you.
Both things are true. Both are the deal.
The people who ride the ride all the way through — including the parts they hate — are the ones who eventually get off with something built. The people who try to only enjoy the highs and skip the lows get off at the first drop and never come back.