Everyone tells you to start a side project. Nobody tells you how to pick one that you’ll actually finish.

I’ve started about twenty side projects over the past five years. I’ve finished four. Those four taught me more than any course or book. The sixteen I abandoned taught me what doesn’t work.

Why Most Side Projects Fail

The pattern is always the same. You get excited about an idea on Friday night. You spend the weekend working on it. By Wednesday, the excitement has faded and real work is demanding your attention. The project sits untouched for two weeks. Then you feel guilty about it, which makes you avoid it more. Eventually you start a new project and the cycle repeats.

The problem isn’t discipline. It’s project selection.

The Right Size Matters

The projects that succeed are small enough to complete in a reasonable timeframe but meaningful enough to keep your interest.

A weekend project should be genuinely completable in a weekend. Not “I’ll build the MVP this weekend and iterate later.” That’s a multi-month project in disguise.

A month-long project should have clear, achievable milestones. Each milestone should produce something usable, not just progress toward a distant goal.

If you can’t describe the finished product in two sentences, the project is probably too ambitious.

Scratch Your Own Itch

The best side projects solve a problem you actually have.

I built a simple script that automatically organises my downloads folder by file type. It took an afternoon. It saves me ten minutes a day. It also taught me file system operations in Python.

I built a basic expense tracker because every app I tried was either too simple or too complex. It taught me database design, user authentication, and basic frontend work.

Neither of these would impress anyone on a portfolio. Both were genuinely useful and educational.

Learning Through Building

Side projects teach differently from courses. Courses give you knowledge in a structured sequence. Projects throw problems at you in random order.

You’re building a web app and suddenly you need to figure out deployment. Then you need to handle file uploads. Then you discover your database queries are slow and you need to learn about indexing.

This messy, non-linear learning is uncomfortable but effective. It mirrors how real work actually happens.

Projects That Develop Useful Skills

If you want your side project to develop career-relevant skills, choose something that forces you into areas you’re weak in.

If you’re a backend developer, build something with a frontend. If you’re a designer, build something functional. If you’re in marketing, build something technical.

The discomfort is the point. You already know how to do things in your comfort zone.

Some project ideas that develop broadly useful skills:

Build a personal website from scratch (not WordPress). Forces you to learn HTML, CSS, hosting, and deployment.

Automate something at work with a script. Forces you to learn a scripting language and understand APIs.

Build a data dashboard for something you’re interested in (sports stats, stock prices, weather data). Forces you to learn data handling and visualisation.

Create a newsletter on a niche topic. Forces you to learn about content, distribution, and audience building.

The Portfolio Effect

Even small side projects demonstrate something important to employers and clients: initiative.

The person who built three small, completed projects shows more than the person who started one ambitious project that never launched.

Completion is the differentiator. Anyone can start things. Finishing them, even if they’re imperfect, is rare and valuable.

The Permission to Quit

Sometimes the right move is to abandon a project. Not every idea deserves your time.

If you’ve been working on something for two weeks and it’s not teaching you anything new or solving a problem you care about, drop it. There’s no obligation to finish.

The key is honesty. Are you quitting because it’s hard (push through) or because it’s not the right project (let it go)?

Start Small Today

Pick something you can build this weekend. Not next weekend. This weekend.

Make it small. Make it useful to you. Don’t worry about whether anyone else would care about it.

The value isn’t in the finished product. It’s in what you learn while building it.