I’ve been building out my own creator store, a place where I can share and sell things that have genuinely helped me improve as a developer and as a person.
This includes:
<ul>
<li>Obsidian templates and systems</li>
<li>Custom dashboards and workflows</li>
<li>Canvas maps and flow structures</li>
<li>Dev environment setups (like Neovim configs)</li>
</ul>
The goal is simple:
<blockquote>
Give people tools that actually improve their systems and thinking, not just surface-level content.
</blockquote>
<h2>What I Thought Going In</h2>
I came into this project thinking:
<ul>
<li>“Frontend is the hard part.”</li>
<li>“Backend is just connecting things.”</li>
<li>“Database is just storing data.”</li>
</ul>
I was wrong.
<h2>Reality Check: Backend &amp; Database Work</h2>
Once I started actually building this out, especially with:
<ul>
<li>APIs</li>
<li>Database structure (MongoDB clusters)</li>
<li>Schema design (Prisma)</li>
<li>Handling multiple apps sharing data</li>
</ul>
I realized something important:
Backend and database work is essentially its own specialization.*
It’s not just “plugging things in.”
It’s about:
<ul>
<li>Structuring data correctly from the start</li>
<li>Preventing conflicts across systems</li>
<li>Designing for scalability</li>
<li>Understanding how everything connects under the hood</li>
</ul>
And honestly… this is where I got humbled.
<h2>The Struggle Phase</h2>
I hit issues like:
<ul>
<li>Things are not connecting properly</li>
<li>Data not structured the way I expected</li>
<li>Clusters are getting messy and hard to read</li>
<li>Realizing I didn’t fully understand how everything flowed together</li>
</ul>
And that feeling of:
<blockquote>
“Wait… I thought I was further ahead than this.”
</blockquote>
That part is tough.
But also necessary.
<h2>The Shift in Perspective</h2>
Instead of seeing this as a setback, I’m starting to see it as a directional correction.
Now I know:
<ul>
<li>Where are my gaps actually</li>
<li>What I need to study deeply (not just skim)</li>
<li>That backend + database knowledge is non-negotiable for what I want to build</li>
</ul>
This is the kind of realization you can’t fake your way through.
<h2>Why This Store Matters (Beyond Just Selling)</h2>
This store isn’t just about products.
It’s connected to everything I’m building:
<ul>
<li>My systems</li>
<li>My learning process</li>
<li>My Patreon journey</li>
</ul>
One thing I’m working toward is:
<blockquote>
Integrating Patreon with the store
</blockquote>
So that:
<ul>
<li>Higher-tier members get discounts or free access</li>
<li>Supporters of the journey get real value back</li>
<li>The ecosystem feels connected, not separate</li>
</ul>
That’s something I haven’t seen done in a way that feels personal and meaningful, so I want to build it that way.
<h2>Where I’m At Right Now</h2>
<ul>
<li>Frontend → progressing well</li>
<li>Backend → actively learning and rebuilding understanding</li>
<li>Database → biggest focus area right now</li>
</ul>
This is the phase where things slow down…
but also where the real skill-building happens.
<h2>Final Thought</h2>
This project reminded me of something important:
<blockquote>
You don’t actually know your level until you try to build something real.
</blockquote>
And right now, I’m in that phase of:
<ul>
<li>Learning</li>
<li>Struggling</li>
<li>Adjusting</li>
</ul>
But also leveling up in a way that actually matters.
More updates soon as I keep pushing through this 👨‍💻

Developer's Journey is a place where we share our stories, career growth, technical adventures, and personal milestones, no matter where we are in our journey.

Developer's Journey

A developer shares their experience building a personal creator store to sell productivity tools and templates. They reflect on underestimating backend and database complexity, hitting real struggles with MongoDB clusters, Prisma schema design, and multi-app data sharing. The post frames these challenges as a necessary learning phase and outlines plans to integrate Patreon membership tiers with the store for a connected ecosystem.

My Journey Making a Ecommerce's store

I’ve been where you are more times than I can count. It’s an ongoing challenge, and there’s always something new to learn, which can feel overwhelming at times. But that’s also what makes it rewarding. If you genuinely enjoy the work, you’ll come to appreciate the process and grow from it, just like I have. Keep up the great work!

thanks for sharing your experience, is a good Feedback!

Keep going I am also building an e commerce store and yes database has been the far most challenging part.

Yo what’s it called I’d like to check it out

sick, do let me know one when you’re done I would like to see what cool stuff you got.