100 Days of Code: My Journey, Projects, and What I Learned

100 days. One commitment. A changed developer.

I decided to take on the #100DaysOfCode challenge not just as a trend, but as a personal contract. I wanted to:

Build discipline
Sharpen my development skills
Create meaningful projects
Grow my confidence in public

What started as a challenge turned into a journey of self-discovery and growth that reshaped the way I learn, build, and think as a developer.

Here’s the story.

Why I Started

Like many developers, I used to code sporadically.

One day, I saw the hashtag #100DaysOfCode trending on X and decided to dive in. It wasn’t about building a perfect portfolio. It was about consistency over complexity.

I promised myself:

I’d code every single day for 100 days
I’d tweet daily logs
I’d reflect and write after the challenge

And I stuck to it.

How I Structured My Challenge

To avoid burnout, I broke the challenge down like this:

Days 1–20: Core JavaScript projects
Days 21–40: DOM manipulation, small apps
Days 41–60: APIs and real-world apps
Days 61–80: React, component-based projects
Days 81–100: Full-stack and polished mini tools

Each day, I coded for 1–3 hours depending on my availability, but I never skipped. I kept it realistic and progress-based, not perfection-based.

Projects I Built

Here are a few highlights:

🔹 Day 5: Tip Calculator

🔹 Day 12: Weather App using OpenWeather API

🔹 Day 28: Expense Tracker with Local Storage

🔹 Day 45: Movie Search App (OMDb API + Vanilla JS)

🔹 Day 59: Notes App with CRUD features

🔹 Day 75: React Task Manager

🔹 Day 83: Blog CMS (with Markdown support)

🔹 Day 96: Portfolio site from scratch

🔹 Day 100: Fullstack Auth Dashboard using Node.js + MongoDB

I compiled these into an eBook with source code, detailed explanations, and project breakdowns:

👉 Get the “100 JavaScript Projects” eBook here

Lessons I Learned

1. Consistency Beats Motivation

There were days I felt uninspired. But I showed up anyway.

That’s where real growth came from.

2. Small Wins Matter

Finishing a to-do app may not seem grand—but building and shipping something every day built momentum.

3. Imposter Syndrome Is Part of the Process

Even on Day 60, I questioned my skills. But I learned that doubt doesn’t mean you’re not growing—it often means you're expanding your boundaries.

4. You Learn by Building

Nothing teaches you React faster than trying to build a working React app.

Nothing teaches you the DOM like debugging real bugs.

5. Sharing Accelerates Growth

Posting daily progress on social media helped me stay accountable and connect with other devs who supported and challenged me.

Advice If You Want to Try #100DaysOfCode

Plan but stay flexible. Life happens. Just keep showing up.
Start simple. Don’t aim to build an Instagram clone on Day 3.
Join a community. Twitter, Discord, dev.to—connect with others.
Celebrate small wins. Push that Git commit. Tweet that Day 14 update.
Document everything. I wish I journaled more during the journey—so start a blog, a thread, or a GitHub repo.

My Biggest Takeaway

I didn’t become an expert in 100 days.

But I became consistent, confident, and creative.

I built projects I never thought I could. I shipped code daily.

Most importantly, I proved to myself that I could grow through commitment.

Whether you're a beginner or an intermediate dev stuck in tutorial hell, I highly recommend doing your own version of #100DaysOfCode.

Want to Learn by Building?

I’ve bundled 100 JavaScript Projects—from beginner to advanced, with source code, explanations, and project ideas for every level.

This eBook is based on my journey and perfect for developers looking to build fast and learn deeply.

🎉 Get the “100 JavaScript Projects” eBook here →

Let’s Connect

I share more dev tips, code breakdowns, project ideas, and motivation here:

🐦 Follow me on X (Twitter) → @e_opore

Feel free to reach out. Ask me questions. Share your own journey.

Let’s grow together.

— Dhanian

100 Days of Code: My Journey, Projects, and What I Learned