Back to Blog

Why I Chose to Build Solo Again After 3 Years Working in a Team

Royan Gagas
June 2, 2025
Share
personal
journey
Why I Chose to Build Solo Again After 3 Years Working in a Team

After years of relying on a great team, I finally decided to go solo again (build my platform). Here's what I realized and why this journey matters for my growth.

After almost 3 years working in a team, this time I decided to build a project solo for my platform.

Why?

Because I want to challenge myself with problems that I don't usually face at work. to bank more knowledge and grow faster.

Here are a few things I realized from working in a team:

1.The Project already set up 🧱 You don't have to deal with initial setup. like environments, config, or dependecies. You just jump in and start coding.
2.Function already to use 🧠 Want to save something to localStorage? Just call a utility function, pass the params, and you're done. Even on the backend, if there's an existing query, you just reuse it.
3.Patterns are established 🧩 Need to build a new service? You can follow the existing pattern. Copy, tweak, done. No need to think to much, fast execution.
4.When errors happen, the team has your back 👥 Because your teammates know the codebase well, debugging feels easier. You're not stuck alone.
5.Fast development Most task are CRUD-based. With the setup ready, development moves quickly.

But now that I'm working from scratch again. I struggled at first. Why? I guess I got too used to the comfort of working in a team.

They say comfort zone is dangeroues if you want to grow. And get it now.

Still, I'm grateful to my team. That experience helped me a lot.

Now it's time to level up⬆️ on my own.

How about you? What kind of teammates do you have? Let me know your experience.