At the beginning of this year, I embarked on the #100DaysOfCode challenge with the goal of sharpening my programming skills, building real-world projects, and developing the discipline of daily coding. As the year draws to a close, I find myself in a similar position—looking back at another attempt at the challenge, acknowledging the wins, the setbacks, and the invaluable lessons learned along the way.
While I didn’t complete either of my #100DaysOfCode attempts in full, I don’t consider them failures. Instead, they were stepping stones in my journey as a developer. They helped me shake off the rust, refine my approach to learning, and, most importantly, build projects that I can now showcase as part of my portfolio. This post serves as a post-mortem of both attempts—what worked, what didn’t, and how I plan to move forward with a renewed sense of purpose.
The First Attempt: Early Year Challenges
When I kicked off my first #100DaysOfCode attempt at the beginning of the year, I was full of energy and enthusiasm. My roadmap was clear: work on projects from freeCodeCamp, Boot.dev, and The Odin Project while documenting my progress. However, as life often does, things got in the way.
What Went Well:
- Consistency (At First): I managed to maintain a solid streak for the first few weeks, reinforcing my coding fundamentals and solving algorithm challenges daily.
- Small Wins: Even though I didn’t reach the full 100 days, I built a few projects that strengthened my portfolio.
- Content Creation Aspirations: I dabbled in writing about my coding journey, which planted the seed for future content creation goals.
What Went Wrong:
- Burnout and Fatigue: Balancing work, job hunting, and learning took a toll on my motivation and energy levels.
- Lack of Structure: I didn’t define clear milestones for my projects, which led to aimless coding sessions at times.
- Overcommitment: I tried to do too many things at once—courses, projects, and algorithms—without a clear priority list.
By the time I realized I was slipping, I had already lost momentum. Instead of forcing myself to continue aimlessly, I decided to take a step back, reevaluate my approach, and prepare for another run later in the year.
The Second Attempt: Later in the Year, New Perspective
Determined to give #100DaysOfCode another shot, I restarted the challenge later in the year with a fresh mindset. This time, I focused on practical application—building projects that I could showcase rather than just grinding tutorials.
What Went Well:
- Project-Based Learning: Instead of getting lost in endless theory, I focused on developing functional applications that solved real problems.
- Better Time Management: I learned from my past mistakes and allocated time more effectively, making coding a structured part of my day.
- Stronger Foundation: Revisiting concepts from earlier in the year helped solidify my knowledge, making me a more confident developer.
What Still Needs Work:
- Sticking to the Habit: While I improved my time management, I still struggled with consistency during busy weeks.
- Publishing My Work: I built more projects, but I haven’t showcased them properly—something I aim to fix soon.
- Overcoming Self-Doubt: Impostor syndrome hit harder this time, especially when comparing myself to others who completed the challenge flawlessly.
Even though I didn’t complete 100 days straight, I consider this attempt a success because it brought me closer to my goal: becoming a better developer and building things that matter.
Moving Forward: Clearing the Rust and Showcasing My Work
Now that the year is coming to a close, my focus is shifting toward two key objectives:
- Clearing the Rust: While I’ve kept my programming skills sharp, there’s always room for improvement. I plan to refine my coding workflow, revisit fundamental concepts, and ensure that I have a strong grasp of both front-end and back-end development.
- Showcasing My Projects: I have a collection of unfinished and completed projects that deserve to be shared. I’ll be dedicating time to polishing them, writing about them, and potentially turning them into content pieces for my blog and portfolio.
The journey doesn’t end just because the challenge wasn’t completed in its traditional form. In fact, it’s only just beginning.
Final Thoughts: The Real Value of #100DaysOfCode
If there’s one key takeaway from my experience with #100DaysOfCode, it’s that the challenge is not about perfection—it’s about progress. The goal isn’t just to reach 100 days but to build a lifelong habit of coding, learning, and growing as a developer.
For anyone considering the challenge, I’d say this: don’t be discouraged if you don’t complete it. The true value lies in the lessons you learn along the way. Whether you make it to Day 100 or stop at Day 30, every line of code you write is a step forward.
As for me, I’m embracing the unfinished business and turning it into fuel for the next phase of my journey. 2025 will be a year of execution, and I can’t wait to see where it takes me.
What’s Next?
In the coming weeks, I’ll be sharing my projects, my plans for refining my skills, and my roadmap for 2025. Stay tuned for updates, and if you’re on a similar journey, let’s connect and grow together!
Have you attempted #100DaysOfCode? What was your experience like? Drop a comment and let’s discuss!