Most advice about building side projects comes from people who've already made it. They've quit their jobs, raised funding, or have enough savings to take a year off. Good for them, but that's not helpful when you've got a full-time job, you're tired after dinner, and you've maybe got two hours before you need to sleep.
I've built several apps while working full-time. Not because I have superhuman discipline, but because I figured out what actually works when your time and energy are limited. None of this is glamorous. All of it is practical.
The biggest shift for me was letting go of the idea that I needed to build things "properly" before showing anyone.
AI tools changed everything. I can go from idea to working prototype in an evening now. Not polished, not scalable, not pretty, but functional enough to get feedback. That's the only thing that matters early on. Does anyone actually want this?
I used to spend weeks building something in isolation, convinced I needed to get it right before anyone saw it. Now I build the ugliest possible version that demonstrates the idea, then put it in front of people immediately. Most of my ideas die at this stage, which is the point. Better to find out in a weekend than after three months of evenings.
When you're tired and you've only got an hour or two, "build the app" is paralysing. You won't start because the finish line is too far away.
Instead, I set goals I can hit in a single session. "By tonight, the blog page works." "By tomorrow, users can log in." That's it. Not the whole feature, not the whole product. Just the next concrete thing.
You need wins to keep momentum going. If your goals are too big, you'll go weeks without one, and eventually you'll stop opening the laptop altogether. Small goals compound. You look up after a month and realise you've actually built something.
I tried the "work on your side project every day from 8–10pm" approach. It doesn't work for me. Some nights I sit down and I've got nothing. Other nights I look up and it's 1am and I don't want to stop.
Now I follow my energy instead of fighting it. If I'm in flow, I let myself stay there. If I'm not feeling it, I do something small or I stop entirely. No guilt.
This only works if you've got small goals. When the bar is low, even your worst evening can clear it. And when you're on fire, you blow past it and keep going.
This one's uncomfortable, but it's probably the most important.
Show people your work before it's finished. Before it's polished. Before you're proud of it. The longer you wait, the more attached you get, and the harder feedback becomes to hear.
I've learned to separate myself from the work. When someone says "I don't get it" or "I wouldn't use this," they're not criticising me. They're giving me information about the idea. That information is gold. It tells me whether to keep going or move on.
The people who build in silence for months and then launch to crickets? They skipped this step. Get out of your comfort zone. Show someone your half-finished thing. It's not about you, it's about whether the idea works.
I used to catch myself thinking things like "but what if 10,000 people sign up and the database can't handle it?"
Mate, you'd be lucky. That's a champagne problem. You're not there yet. Neither am I.
Worrying about scale before you've validated anything is just procrastination dressed up as planning. It feels productive because you're thinking about architecture and infrastructure, but really you're avoiding the hard part: finding out if anyone wants what you're building.
Validate first. Get users. Get feedback. Get traction. Scaling problems are good problems to have, and you can solve them when they actually arrive.
I'm not going to pretend it's easy. Some weeks I make loads of progress. Some weeks I open my laptop once, stare at the screen, and close it again.
But I've shipped things. Real things that real people use. Not because I'm special, but because I lowered the bar enough to keep going. Quick prototypes. Tiny goals. Following energy. Asking for feedback. Not overthinking scale.
You don't need to quit your job to build something. You need a free evening, a small goal, and the willingness to show someone your ugly work before it's ready.
Now go build something.
Whether you need a full build or just a second opinion, I'm here to help. No pressure, no jargon.
Get in touch