Let’s be honest: starting a coding challenge is easy. Opening your IDE on Day 1 with high hopes, clean folders, and big dreams takes zero effort. But what happens when Day 15 rolls around, life gets chaotic, and your logic breaks at midnight?
Over the last 60 days, I decided to stop just reading about development concepts and actually build things out in the open. I pushed code step-by-step to my GitHub account (@ayindeyusuf1999-max), dealt with the messy reality of debugging, and came out the other side with a clearer head and stronger skills.
Here is the honest breakdown of how the journey went, what I learned, and why building in public changes everything.
Why I Decided to Share My GitHub Account
When writing a tech blog or sharing a milestone, dropping a link to your repository is the ultimate proof of work. Anyone can write about how they planned to code, but green contribution squares and commit histories don't lie.
