I've started and abandoned more side projects than I can count. Each time it was the same story: burst of enthusiasm for a week, then life gets busy, I skip a few days, and suddenly it's been three months since I touched the repo.

At some point I realized the problem wasn't my project ideas. It was me expecting motivation to carry me through. Motivation is great for starting things. It's terrible for finishing them.

What finally worked was giving up on motivation entirely and building systems instead. Boring? Yes. Effective? Also yes.

The Problem With "Finding Time"

"I'll code when I have a few free hours" is the kiss of death for any habit. Free hours don't exist. Something always fills them. Netflix. Errands. That thing you forgot to do. Before you know it, it's 10 PM and you're too tired.

I wasted years waiting for the perfect 4-hour block to get into "flow state." Here's what I learned: flow state is nice but optional. Most of my actual progress happened in shorter sessions where I just... started.

The hardest part of coding isn't the coding. It's opening the laptop. Once you're in the editor, fingers on keyboard, something usually happens. But getting there? That's the real battle.

15 Minutes Is Enough (Seriously)

My current rule: I have to code for 15 minutes. That's it. After 15 minutes, I'm allowed to stop.

I almost never stop at 15 minutes.

But knowing I can stop removes the dread. "Ugh, I have to code for two hours" is paralyzing. "I just need to do 15 minutes" is manageable. And once you're in the code, momentum takes over.

This isn't some productivity guru nonsense. It's physics. Objects at rest stay at rest. Objects in motion stay in motion. The 15-minute commitment is just a way to overcome initial friction.

Making It Automatic

I stole this trick from somewhere (probably a book I half-read): attach the new habit to something you already do. Habit researchers call this "stacking" or "chaining." I call it "not having to think about it."

For me, it's coffee. Every morning I make coffee. While it brews, I open my laptop and start my dev environment. By the time I have coffee in hand, I'm already looking at code. There's no decision point. No "should I code or check Twitter first?" It's just what happens after I press the button on the coffee maker.

Find your trigger. Maybe it's after lunch. Maybe it's after putting kids to bed. Doesn't matter what it is, as long as it's consistent and you don't have to think about it.

The Environment Hack

Here's a small thing that made a big difference: I made starting fast. 

# In my .zshrc
alias dev="cd ~/projects/current && code . && npm run dev"

One command. Terminal, editor, dev server, all running. No hunting for folders. No remembering what I was working on. Just type `dev` and I'm in.

I also leave the editor in a specific state when I stop. Usually there's a failing test or a TODO comment with exactly what I need to do next. 

// TODO: Next session - add validation for email field
// The regex is in utils/validators.js, just need to wire it up
test('rejects invalid email', () => {
  expect(true).toBe(false); // make this pass
});

When I come back, I don't have to remember anything. The code tells me what to do. I'm productive in the first minute instead of spending 10 minutes going "wait, where was I?"

What About Bad Days?

You will miss days. This is fine. The goal isn't a perfect streak. The goal is not losing momentum entirely.

My rule: never miss twice in a row. Miss Monday? Fine, happens. But I have to do something Tuesday. Even if "something" is just reading one function and adding a comment. The point is to keep the habit alive.

Streaks are motivating until they're not. Once you break a 30-day streak, it feels like the whole thing is ruined. "I already failed, might as well skip today too." This is dumb but human. The "never two in a row" rule avoids that trap.

What to Work On

Sometimes I sit down and realize I don't know what to code. The project feels overwhelming. I end up browsing GitHub issues instead of actually writing code.

Two things help here. First, I keep a running list of small tasks. Not big features - tiny things. "Add loading spinner to button." "Fix that console warning." "Write one more test." When I'm stuck, I pick something from the list that I can finish in 15 minutes.

Second, I keep a simple log. Just a text file. 

# dev-log.md

## June 11
- Finally fixed the auth bug. Was a race condition in the token refresh.
- Realized the user list needs pagination, added to backlog.

## June 10  
- Set up testing environment. Jest config took forever.
- Note to self: `moduleNameMapper` is case-sensitive on Linux.

This serves two purposes. It shows me I'm making progress (important for morale). And it helps me pick up where I left off after a break.

When Coding Feels Like a Chore

If you consistently dread your coding sessions, something's wrong. Maybe the project isn't interesting anymore. Maybe you're burned out. Maybe you just need a break.

Hobbies are supposed to be enjoyable. If coding outside of work feels like more work, it's okay to step back. Watch some tech talks instead. Read blog posts. Mess around with a completely different language just for fun. The point is to stay engaged with programming, not to turn it into a second job.

I take breaks. Sometimes a week, sometimes a month. The routine is there when I come back. It doesn't judge me for leaving.

A Year From Now

Small consistent effort beats sporadic marathons. If you code for 20 minutes most days, that's about 120 hours a year. More than enough to learn a new framework, build a portfolio project, or contribute to open source.

The developers who seem to have endless side projects aren't coding 8 hours on weekends. They're coding a little bit, regularly, for years. It adds up.

Start small. Be patient with yourself. And remember: 15 minutes counts.

Back to Developer Productivity

Back to Home