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. As of February 14, I've written all 100 articles of my Python 100-Day Challenge on note.com.

01Why I started

I started a Python 100-Day Challenge on note.com, a blog platform that's popular in Japan. The idea: one article a day, 100 learning logs in total, from Python basics to an intro to AI/ML.

Honestly, at first there was some marketing math in it: "If I keep making programming content, maybe I'll gain followers on note.com and it'll help people find Park Labs." But once I got going, the habit of writing every day turned out to be worth more than any of that.

02How the 100 days were structured

I split it into 10 phases.

Table 1

I also made a guide by goal, "so beginners can pick what to read." Just want the syntax? Read up to Phase 2. Want data analysis? Up to Phase 8. That kind of thing.

03I almost gave up halfway

The closest call was around Day 50. It was the New Year holidays, and I drank way too much over New Year's and completely crashed. I couldn't write that day, and because of the "100 days in a row" pressure, the feeling of "I failed" hit much harder than I expected. It knocked me down pretty badly.

But I realized something there. A 100-day streak matters, but finishing matters more. So I pulled myself together and started again. There were days I took a day or two off and days I wrote several at once. It actually took longer than 100 days, enough to make the name "100-Day Challenge" a little embarrassing.

Still, I wrote all 100. It was something like stubbornness: "I've come this far, so let's give it a finished shape."

04The response

The final Day 100 post got 175 likes (スキ) and 16 comments. Not a bad response for note.com. Some people left feedback in the comments along the way, and every one of those really kept me going. Whenever I was about to quit, a notification would come in, I'd think "oh, someone's actually reading this," and I'd write again.

05What I learned

Technically, I didn't learn much that was new. I'm a software engineer by trade. What I did feel, painfully, was how hard it is to explain what you know in a way others can easily follow. "Who's going to read this?" and "isn't this too thin?" crossed my mind every single day.

And the power of a daily writing habit. Even when I'm tired after work and nothing comes to mind, if I just sit down and start writing, it works out somehow. It doesn't have to be perfect. It's okay to take breaks. What matters is getting to the end.

06What's next

These 100 articles aren't one-and-done. I plan to keep improving them: working in feedback, adding diagrams, making videos.

For the next content, I'm thinking about a personal project diary, a weekly IT trends roundup and tips for using AI. All of it based on things I'm actually doing.

The biggest thing I felt while writing those 100 articles is that the moment you think it's too late is actually the earliest you can start. A cliché, but it turned out to be true.