30 Days of #100DaysOfCode: One Month Review

Thirty days in. Seventy to go.

I want to write an honest review of the first month — what I learned, what surprised me, and what I'd tell someone starting this challenge today.

What I completed

You Don't Know JS — I finished the first three books (Up & Going, Scope & Closures, this & Object Prototypes) and started the fourth. Kyle Simpson writes differently from most JavaScript authors. He's not trying to teach you how to use JavaScript — he's trying to teach you how JavaScript works. That distinction matters. I understand things now that I used to just accept.

Harvard CS50 — Two weeks in. The lectures are excellent and free, and Professor Malan makes computer science feel approachable without making it feel shallow. Recommended for anyone who, like me, has gaps in their CS fundamentals.

Three projects built:

• A personal portfolio site (my first real attempt at designing something for myself)
• A web design agency clone (studying how real agency sites are structured)
• A conference website (from Shay Howe's HTML & CSS course)

None of them are impressive by any standard. But building them while learning meant I had to solve real problems — not just follow a tutorial step by step.

What I learned about learning

You can't learn a whole language in a month. I knew this before I started, but living it is different. There are still concepts in JavaScript I don't fully understand. There are things in CS50 that I've heard of but can't implement from scratch yet. That's fine. It's supposed to be that way.

The mistake most beginners make is thinking that confusion means failure. It doesn't. Confusion means you've reached the edge of your current understanding. That's the exact right place to be.

What I started doing differently: when something doesn't click after a reasonable amount of time, I switch to a different resource. A YouTube video. A Stack Overflow thread. A different explanation in plain English. Fighting a wall for hours is not learning — it's just frustration. Get what you need to move forward, and come back to the hard part later.

What changed in 30 days

I code every day now. Not because of the challenge — because it became the default. The challenge gave me the structure to build the habit, but at some point the habit became its own thing.

I also started thinking differently. I notice things about websites I use — how they're structured, where the spacing feels off, what makes an interface feel right or wrong. That might sound unrelated to learning JavaScript fundamentals, but I think they're connected. Building things makes you observe things. Observing things makes you build better things.

What's next

The challenge continues. More YDKJS. More projects. I want to build something real — not a tutorial project, not a clone. Something I actually want to exist.

That's the real goal: not to finish the challenge, but to become someone who builds things worth building.

Thirty down. Seventy to go.