Should I do a side project while working full-time?

Not if you're burned out. But if you have energy: yes. Side projects build skills, portfolio, network, and confidence in ways your job can't.

What makes a good side project?

Something you'll actually finish. Something that teaches you something. Ideally, something you can show to people. Length doesn't matter; completion does.

How much time should I spend on side projects?

5-10 hours a week is realistic for working full-time. You don't need to sacrifice sleep. You need to stop doom-scrolling instead.

Should my side project make money?

Not necessarily. But it should teach you something or build your portfolio. Money is a bonus, not the point.

What if I fail at my side project?

You've learned what doesn't work. You have code/writing/work to show. That's not failure; that's data and a portfolio piece.

Will side projects hurt my job performance?

Only if you prioritize them over work. If you're managing both well: no. In fact, the energy and learning from side projects often improves job performance.

Should I tell my manager about side projects?

Usually yes. Good managers want you to grow. But check your contract first—some companies restrict outside work.

What's the difference between a hobby and a side project?

A hobby is for fun. A side project has an audience or learning goal. Both are valuable, but side projects are career-accelerating.

The Role of Side Projects in Career Development

Your day job teaches you one thing. Side projects teach you everything else. Here's why they matter.

Your job teaches you how to do your job. It doesn't necessarily teach you how to grow beyond it.

Side projects teach you things your job can't: How to own something entirely. How to ship incomplete work. How to get feedback from real people. How to learn technologies your employer doesn't use. How to build in public.

Side projects are the fastest way to accelerate your career. Not because they make you money (usually they don't). But because they make you capable.

This guide walks you through why side projects matter and how to choose ones that actually accelerate your career.

Why Side Projects Matter

Your day job:

Teaches you one company's way of doing things
Uses one tech stack or discipline
Is constrained by organizational processes
Doesn't require you to think about users, marketing, or business
Is often passive (you're assigned projects)

Side projects:

Teach you how to ship something
Let you use new tools and technologies
Force you to think about the whole picture (design, marketing, business)
Let you own something end-to-end
Are active (you decide what to build)

The advantage: Side projects expose you to the parts of your field you don't see at work.

Engineer learning design? You pick up UX, marketing, and business thinking. Not because you need to, but because shipping something forces you to.

Designer learning how code actually works? You understand constraints. You build better designs.

Writer building a community? You learn how to market, monetize, and sustain something.

Side projects are how you become well-rounded. And well-rounded people move faster.

Side Projects Build Your Leverage

Your job history gets you interviews. Your portfolio gets you offers.

Side projects are portfolio. They're proof.

Proof of what?

You can ship something (not just talk about it)
You can learn something new (not just do what you know)
You can sustain effort over time (not just a weekend project)
You can take feedback and iterate
You care enough to do work that's not assigned

All of this is leverage. It's what gets you:

Higher salary offers (companies see proof of capability)
Better jobs (startups want people who've shipped things)
More confidence (you know you can build things)
Faster growth (you skip the learning curve on the job)

How to Choose a Side Project

Not all side projects are worth your time. Some will fizzle. Some will teach you nothing.

Good side project criteria:

You'll actually finish it. Not "would like to" but genuinely will. This is the most important filter. An incomplete ambitious project teaches you nothing. A simple completed project teaches you everything.
It teaches you something. New technology, new skill, new domain. You're learning, not just executing.
You can show it to people. A blog post, a GitHub repo, a deployed app. Something tangible that shows what you built.
It solves a real problem. For you, for friends, for a community. Not "wouldn't it be cool" but "people actually need this."
It has a reasonable scope. Not a startup (you'll never finish). Not a weekend project (you'll learn nothing). 3-6 months of 5-10 hrs/week is the sweet spot.

Examples of good side projects:

A simple tool that solves a problem you have (and others probably have)
A portfolio piece showing skills you want to demonstrate
A contribution to open source over 3-6 months
A newsletter on a topic you know well
A course or guide teaching something you've learned
An experiment testing an idea (doesn't need to last forever)

Examples of bad side projects:

Recreating a big company's product (too much scope)
A "startup" where you expect it to be your next income source
Something others told you to build (not your genuine interest)
Something so niche nobody else cares (no feedback loop)

The Side Project Rhythm

Month 1: Clarity

Define what you're building (clearly)
Understand who it's for (even if it's just you)
Set a realistic shipping date (6 months max)
Plan the absolute minimum version

Months 2-4: Building

5-10 hours a week consistent work
Show progress to people (get feedback early)
Adjust based on feedback
Don't perfectionism this to death

Month 5-6: Shipping and Beyond

Get it out there (even if it's not perfect)
Get feedback from real users
Iterate based on feedback
Market it a bit (talk about what you've learned)

Month 7+: Maintain or Sunset

Keep improving if you're still motivated
Or wrap it up and move to the next project
Either way, you have a portfolio piece

Side Project + Full-Time Work

People worry: "If I do side projects, will my job suffer?"

Only if you're bad at time management. Here's the reality:

You have enough hours. A full-time job is 40 hours. Sleep is 56 hours. That leaves 72 hours. 5-10 hours of side projects and you still have 62 hours. You're not suffering. You're just not doom-scrolling.

Side projects energize you. Working on something you own, something you're learning from—it actually makes you better at your day job. You're learning faster. You're more confident. You're more engaged.

Your day job teaches side projects, too. You're using skills from work in your project. You're seeing how the things you learn at work apply to real problems.

The risk: Only do side projects if you have the energy. If you're burned out, the answer is rest, not more work.

The Vulnerability Factor

Side projects are public. People see them. They might not work. You might ship something mediocre.

That's the point.

The side projects that matter are the ones that expose you—show what you're learning, what you're trying, where you're not yet perfect.

Perfection is private. Growth is public.

When you ship a side project, you're saying: "I built this. It's not perfect. Here's what I learned." That kind of vulnerability builds respect.

Side Projects Are Experiments

Not every side project will be a hit. Some will teach you what not to do. Some will flop. Some will surprise you.

That's valuable data.

"I tried to build a course and realized I don't enjoy teaching" is useful. "I built an open-source tool and found I love the community aspect" is useful.

Side projects are how you figure out what you actually like—not what you think you should like.

The Permission You Need

You don't need permission to have a side project. (Check your contract, sure, but mostly you don't.)

You don't need side projects to be successful. Some people go deep at work instead. That's fine.

You don't need your side project to make money. Portfolio and learning are enough.

You don't need to sacrifice your life. 5-10 hours a week. That's reasonable.

You don't need it to be perfect. Done and shipped beats perfect and hidden.

The Side Project Checklist

Before you commit to a side project, check:

[ ] I'll actually do this (honest evaluation)
[ ] It teaches me something I want to learn
[ ] It has a realistic scope (6 months max)
[ ] I can show it to people when done
[ ] I have energy for 5-10 hrs/week (without sacrificing sleep/health)
[ ] It solves a real problem (for me or others)
[ ] My day job won't suffer

If you check 5+ of these, start the project.

Beyond This Article: Track Your Growth

Side projects are how you become more capable. Documenting what you're learning, what you're shipping, and how it's growing your skills—that's powerful.

Opus helps you track goals and skills you're developing across your side projects and day job.

The bottom line: Side projects aren't extra. They're essential for growth. They teach you things your job can't. They build your portfolio. They make you capable.

You don't need to do a startup. You need to ship something. Start small. Finish it. Learn from it. Move to the next one.

Done beats perfect. Shipped beats planned. You grow fastest by building things.