About This Space

Hie, I am Emmanuel. Welcome to my digital learning notebook.

"All my projects used to die in localhost:3000"

I am sure you know the feeling. You spend a weekend building something cool, learn a ton, maybe even get it working. Then it sits on your local machine forever. Maybe you tell yourself you'll "polish it up" before sharing. That polish never comes.

Well lets see if I can change that.

The Philosophy

Learning in Public

Every project here is part of my learning journey. Some work perfectly, others are gloriously broken. All teach something valuable.

Ship Incomplete

Done is better than perfect. If it teaches something or solves a problem, it belongs here. Polish is optional, documentation is too.

Honest Mistakes

I write about what worked and what didn't. The 95% backtest that crashed in production. The optimization that made things slower. Real learning happens in the failures.

Iterate Publicly

Projects evolve. Version 1.0 might be rough, but it's out there. I can improve it incrementally instead of waiting for perfection that never comes.

Why This Matters

We've all seen those portfolio sites with three perfectly polished projects. Beautiful landing pages, flawless demos, zero rough edges. They're impressive, but they're also intimidating and, honestly, a bit misleading.

Real development is messy. It's half-finished features, pivots, experiments that didn't pan out, and ideas that sounded brilliant at 2 AM but questionable in daylight. That's the stuff worth sharing.

If you're learning to code, building side projects, or exploring new technologies, seeing only polished work can make you feel like you're not good enough. The truth is, everyone's learning process looks like chaos. Mine does, yours does, everyone's does.

What You'll Find Here

  • Projects in various states: Some are production-ready, others are proofs of concept held together with duct tape and hope.
  • Writeups about lessons learned: The math behind models, why backtests lie, how I debugged that weird race condition.
  • Experiments and explorations: Testing out new libraries, trying different approaches, seeing what sticks.
  • Honest documentation: What worked, what didn't, what I'd do differently next time.

My Challenge to You

If you're sitting on projects that "aren't ready yet," I encourage you to ship them anyway. Put them on GitHub. Write a quick README. Share them with one person.

Your messy, incomplete project might be exactly what someone else needs to see. It might inspire them, help them solve a problem, or just make them feel less alone in the struggle.

The projects dying on localhost:3000 are the ones the world needs to see most.

Let's Connect

Found something interesting? Have questions about a project? Want to share your own localhost refugee? I'd love to hear from you.