#100DaysOfCode: What Happened After 30 Days
I finished the 100 days.
I didn't write about it when it happened. Partly because I was in the middle of building things and writing felt like stopping. Partly because I wasn't sure what to say yet. Now, a couple of months on, I think I know.
This is the update I meant to write sooner.
What happened between day 30 and day 100
The first 30 days had structure — the P1xt guide, YDKJS, a rhythm of reading and building. Days 30–100 felt looser. I'd internalized the habit by then, so the accountability of the challenge mattered less. What mattered more was the building.
I got through the rest of You Don't Know JS. Finished Types & Grammar, worked through Async & Performance, started ES6 & Beyond. JavaScript started feeling less like a foreign language and more like something I could think in. Not fluent — not yet — but the syntax wasn't the obstacle anymore.
I also started building things that weren't from tutorials.
That shift is bigger than it sounds. Tutorial projects have guardrails. You already know the outcome, and when something breaks, the answer is in the comments section. Building your own thing is different. You make decisions no one else made, hit problems no Stack Overflow thread answers exactly, and have to sit with the discomfort of not knowing what you're doing until you figure it out.
My first real personal project was a simple task management app — nothing original, but completely mine. No tutorial. No starter code. I designed it, built it, broke it, fixed it. It took three times longer than it should have. I learned more from it than from the previous two months combined.
What I got wrong in the first 30 days
Reading back my earlier posts, I was obsessing over the right resources — YDKJS, CS50, P1xt's guide. I stand by all of those. But I was spending too much time preparing to build and not enough time actually building.
There's a version of learning that feels productive but isn't. Reading the right books, watching the right talks, taking notes in the right format. It has the shape of progress without the substance. The only real check is: can you build something that didn't exist before?
I wish I'd started building original projects earlier. Even small, ugly, broken ones.
What I'm doing now
I'm still learning. The 100 days ended but the daily practice didn't — it just became normal. I code every day because I want to, not because a challenge requires it.
Current focus: JavaScript ES6, CSS layout properly (flexbox and grid, not hacks), and starting to look at how real websites are built — not tutorial demos but actual production codebases. I've been picking apart sites I admire, reading the source, understanding the decisions.
I'm also thinking more about design. Not in a formal way — I don't have the vocabulary for it yet. But I notice things now. The spacing on a page. Whether a button feels right to click. Why some interfaces feel easy and others feel like work. I don't know what to do with that noticing yet, but I'm paying attention to it.
What's next
A job. Still the goal. I want to be good enough that someone pays me to build things, and I want to deserve what they pay me.
I have a portfolio site. It's not impressive, but it exists and it has real projects on it. I'm going to keep adding to it, keep making it better, keep building things I can point to.
The 100 days gave me the habit. The months after gave me the confidence that the habit was real — that I'd keep going without the external structure. That's worth more than finishing any challenge.
I'll write again when there's something worth reporting.
Part of the #100DaysOfCode series: Week 1 · Week 2 · 30-Day Review