What it actually takes to build software nights and weekends while holding down a full-time job. What works, what breaks.
I work a deli counter during the day. I build [SocialMate](https://socialmate.studio) at night. Most of the codebase was written between 10pm and 2am. This is not romanticized — it is exactly what it is.
**You have to want to build it more than you want sleep** — not every night, but most nights. The sessions when you're tired are what separate people who ship from people who talk about shipping.
**You have to be ruthless about scope.** You don't have 8 hours. You have 90 minutes on a good night. Every session needs one specific, achievable goal: "Tonight I'm adding the retry button to failed posts" — not "improving the queue."
**The tool has to match the time you have.** 90 minutes with Claude Code produces what used to take a full day. The constraint isn't ability — it's compressing the feedback loop.
**Accumulating context debt.** A week away from the codebase means 20 minutes just remembering where you were. Fix: always end a session with one note: "Next: X."
**Skipping tests because you're tired.** Creates bugs you'll spend three future sessions fixing. Fix: 5 minutes of real browser testing before closing the laptop. Always.
90 minutes × 5 nights × 50 weeks = 375 hours/year. Nearly 10 full-time work weeks of building. It compounds.
Full workflow: [Gilgamesh's Guide Vol. 4](https://socialmate.studio/guides/vibe-coding-with-ai). Free.
Schedule to 16 platforms, manage your team, and grow your audience — all for free. No credit card required.
Create free account →16 platforms · Unlimited posts · Free forever
Comparing tools?
❤️ 2% of every SocialMate subscription goes to SM-Give — our charity initiative. Learn about SM-Give →