Python 100-Day Challenge Complete - 100 Articles on note.com

Committing to write every day for 100 days was no easy decision. But I pulled it off.

🔬 Why I Started

I kicked off a Python 100-Day Challenge on note.com, a popular blog platform in Japan. The plan: one article a day, 100 total, covering everything from Python basics to AI/ML.

Honestly, part of the motivation was marketing — "if I consistently create programming content, maybe I'll grow followers on note.com and build awareness for Park Labs." But once I got into it, the habit of writing daily turned out to be more valuable than any of that.

🚀 How the 100 Days Were Structured

Split into 10 phases:

- Phase 1~2 (Day 1~20) — Python basics, variables, data types

- Phase 3~4 (Day 21~40) — Control flow, functions, file handling, JSON

- Phase 5~6 (Day 41~60) — OOP, modules, packages, API calls

- Phase 7~8 (Day 61~80) — Pandas data analysis, web scraping

- Phase 9 (Day 81~90) — Flask web dev, REST API, deployment

- Phase 10 (Day 91~100) — scikit-learn, ChatGPT API, AI projects

Also put together a guide so readers could pick and choose based on their goals. Just want syntax? Stop at Phase 2. Data analysis? Phase 8. That kind of thing.

💎 Almost Gave Up Halfway

The closest I came to quitting was around Day 50. It was the New Year's holiday season. Drank way too much on New Year's, completely crashed, couldn't write that day. The "100 consecutive days" pressure hit hard — the feeling of "I failed" was way bigger than I expected. Really knocked me down.

But that's when it clicked. Consecutive days matter, sure, but finishing the whole thing matters more. So I pulled myself together and kept going. There were days I skipped, days I wrote multiple posts to catch up. The "100-day challenge" label feels almost embarrassing since it actually took longer than 100 days.

Still, I wrote all 100. Pure stubbornness — "I've come this far, might as well finish."

📊 How It Landed

The final Day 100 post got 175 likes and 16 comments. Not bad for note.com. Throughout the challenge, people left feedback in the comments, and honestly, every single one of those meant a lot. Whenever I was about to quit, a notification would pop up and I'd think, "someone's actually reading this," and that was enough to keep me going.

💡 What I Learned

Technically, I didn't learn much that was new — I'm a software engineer by trade. What I did learn is how incredibly hard it is to explain things you already know in simple terms. "Who's even going to read this?" and "isn't this too shallow?" — those thoughts showed up every single day.

And the power of a daily writing habit. Even when you're tired after work, even when nothing comes to mind, once you sit down and start typing, something happens. It doesn't have to be perfect. It's okay to take breaks. What matters is finishing.

🎯 What's Next

These 100 articles aren't a one-and-done thing. Planning to keep improving them — incorporating feedback, adding diagrams, maybe creating videos.

For future content, I'm thinking personal project diaries, weekly IT trend roundups, and AI tips. All based on things I'm actually doing.

The biggest takeaway from writing 100 articles — the moment you think it's too late to start is actually the best time. Cliché, but turns out it's true.