With my #100DaysOfCode challenge wrapping up on December 8th, I’m reflecting on my coding progress and stepping into a new chapter—technical writing.As my #100DaysOfCode challenge approaches its conclusion on December 8th, I’ve been reflecting on how much I’ve grown and how far I still want to go. This journey has been about pushing myself out of my comfort zone, tackling coding projects, learning new concepts, and staying committed despite setbacks. Now, as the finish line comes into view, I’m setting my sights on a new goal: sharing my passion for technology through technical writing.
Why Technical Writing?
For me, coding has always been more than just writing lines of logic or solving problems. It’s about the stories behind the process—the why, the how, and the what-if that makes each project unique. Over the past months, I’ve realized that while I love building projects, I’m equally drawn to the idea of communicating those experiences in a way that’s both approachable and impactful.
Technical writing feels like the perfect outlet for this. It allows me to connect with others in the tech community, break down complex concepts, and perhaps even help someone who’s just starting their journey. It’s also a chance for me to solidify my own knowledge—because if you can teach something, you truly understand it.
Where I’m Starting
My plan is to take what I’ve learned during my #100DaysOfCode and translate it into meaningful posts on platforms like LinkedIn, Medium, and my own website. These posts won’t just be tutorials or explanations—they’ll be stories about the challenges I’ve faced, the solutions I’ve found, and the lessons I’ve learned along the way.
I also want to share insights into the tools and resources that have helped me, such as my experiences with freeCodeCamp, Boot.dev, and The Odin Project. I believe these reflections can resonate with others who are self-taught or navigating a non-linear path in tech, just like I am.
Challenges and Hopes
Of course, stepping into technical writing comes with its own challenges. For one, I know I’ll need to refine my writing skills to make my posts clear, concise, and engaging. Then there’s the vulnerability of putting my thoughts out there—what if people don’t find them useful? What if my work isn’t “good enough”?
But the excitement outweighs the fear. I’m motivated by the idea that even a single post could inspire or help someone else. And for me, this isn’t just about building a portfolio—it’s about building connections, growing as a communicator, and giving back to the tech community that has supported me throughout my learning journey.
Looking Ahead
As I take this leap, I’m hopeful that technical writing will become more than just a side project—it’s something I want to incorporate into my career and personal brand. Whether it’s through blog posts, documentation, or even videos down the line, I’m excited to explore where this path can take me.
With the end of my #100DaysOfCode challenge fast approaching, this feels like the right time to embrace something new. I’ll still be coding, learning, and growing, but I’m ready to add another dimension to my journey.
A Call to the Community
To those reading this, whether you’re a fellow coder, a writer, or just someone passionate about learning: I’d love your support and feedback as I take on this next challenge. If you’re a seasoned technical writer or someone who’s been where I am now, I’d be grateful for any advice or insights you can share.
This is just the beginning of what I hope will be a long and rewarding journey. I’ll be sharing updates, articles, and lessons along the way, and I hope you’ll follow along. Here’s to the start of something new—and to turning my passion for coding into stories that matter.