![[The AI Show Episode 143]: ChatGPT Revenue Surge, New AGI Timelines, Amazon’s AI Agent, Claude for Education, Model Context Protocol & LLMs Pass the Turing Test](https://www.marketingaiinstitute.com/hubfs/ep%20143%20cover.png)
_Muhammad_R._Fakhrurrozi_Alamy.jpg?width=1280&auto=webp&quality=80&disable=upscale#)
_NicoElNino_Alamy.jpg?width=1280&auto=webp&quality=80&disable=upscale#)
![AirPods Pro 2 With USB-C Back On Sale for Just $169! [Deal]](https://www.iclarified.com/images/news/96315/96315/96315-640.jpg)
![Apple Releases iOS 18.5 Beta 4 and iPadOS 18.5 Beta 4 [Download]](https://www.iclarified.com/images/news/97145/97145/97145-640.jpg)
![Apple Seeds watchOS 11.5 Beta 4 to Developers [Download]](https://www.iclarified.com/images/news/97147/97147/97147-640.jpg)
![Apple Seeds visionOS 2.5 Beta 4 to Developers [Download]](https://www.iclarified.com/images/news/97150/97150/97150-640.jpg)
100 Days of Code: My Journey, Projects, and What I Learned
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:
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:
