Why Weekend Projects Never Get Finished

Where Does Friday Night's Enthusiasm Go?

Friday, 9 PM. The week is over. I crack open a beer and think "this weekend, I'm building that thing." Peak enthusiasm. Create a new GitHub repo, write a feature list in the README, do the initial setup. create-next-app, Tailwind config. All done in 1 hour 30 minutes. Feeling great.

Saturday morning. Coffee, open laptop, pull up last night's repo. Write some code for 2-3 hours. But after lunch, motivation evaporates. "This is more complex than I thought." "I should think about the design more." Excuses begin.

Sunday. Don't open the code at all. Watch Netflix or nap. Tell myself "next weekend." Next weekend never comes.

Confronting My Repo Graveyard

I counted my GitHub private repos. 23. Of those, actually finished and deployed: 2. The remaining 21 have either just a README and initial setup, or stopped mid-progress. Fourteen haven't been committed to in over 6 months.

The repo names alone tell the story:

• my-budget-app -- Budgeting app. Abandoned after 3 days.
• dev-news-aggregator -- Dev news collector. Built the scraper then stopped.
• pomodoro-cli -- Pomodoro CLI tool. Actually published to npm. Downloads: 7.
• recipe-share -- Recipe sharing app. Only the database schema exists.

Why Does This Keep Happening?

I analyzed it. (Spending time on this analysis is also part of the problem, I know.)

First, the scope is always too big. Not "budget app" but "AI-powered smart budget tracker that analyzes spending patterns and recommends savings strategies." On Friday night, this seems achievable. Saturday afternoon brings reality.

Second, I only want to do the fun parts. Setting up a new framework is fun. Building the first component is fun. But login flow, error handling, deployment config -- the boring stuff is 60% of the work. That's where I stop.

Third, solo means no accountability. Work projects have deadlines and teammates. Side projects? Nobody notices if I quit.

What Made the Two Finished Ones Different?

One is this blog. The bar for "done" was low -- deploy it and add posts over time. Doesn't need to be perfect to ship.

The other was a VS Code extension I built with a coworker. Having a partner meant I couldn't bail. Sharing progress every weekend -- "here's what I did" -- created external pressure.

The pattern: small scope + external accountability. Both present = project gets finished.

What I'm Trying Now

Recently set a "1-week project" rule. Start and finish within a single weekend. One feature. Minimal design. Deployed is the goal.

Last week's project under this rule: "dead simple web app for logging what I ate today." Next.js + localStorage. No server, no database. Started Saturday morning, deployed to Vercel by evening. 127 lines of code.

Is it polished? No. Pretty? No. But it's finished. Deployed. That matters.

What to Do With the Abandoned Repos

I know I should clean them up, but deleting feels wrong. "Maybe I'll come back to it someday." But honestly, a repo untouched for 6 months isn't getting reopened.

Planning to archive them next week. Can't bring myself to delete, but at least they'll be out of sight. And before creating any new repo, I'll ask myself: "Can I deploy this by Sunday evening?"

21 out of 23 being failures is a depressing number. But flip it around: that's energy to start 21 times. The problem isn't energy -- it's direction. Probably.