Skip to main content

Welcome to CodeQuest118

My Journey Through 118 Coding Projects

What do you do when the job market shifts, opportunities shrink, and the confidence you once had feels miles away? For me, the answer isn’t entirely clear yet. But one thing I do know is that I can keep building, learning, and sharing as I figure it all out.

CodeQuest118 is my answer to a challenging job market and a passion I’ve always had for solving puzzles. This is my journey through 118 technology projects—a space where I can grow, experiment, and document everything I learn along the way. Whether anyone else reads this or not, this blog is here to remind me just how far I’ve come. But if you’re here, welcome! I hope it inspires you to build something.

Why CodeQuest118 Exists

I’ve always been a problem solver. I love numbers, data, and getting to the bottom of things. But when I was laid off in late 2022, I decided to take a break. How often do you really get a stress-free career pause?

Then 2023 hit me like an emotional whirlwind and when I finally tried to get back into things, the tech market wasn’t what it used to be. Once upon a time, my LinkedIn inbox would overflow with recruiters. In fact, that’s how I landed my previous role. But now? Crickets. Interviews were few and far between, and when I finally landed one, the process felt like a marathon: multiple rounds of LeetCode, whiteboard coding, and judgment-filled stares.

Let’s pause here—how many developers actually solve LeetCode problems in their day-to-day jobs? I’m a problem solver, not a memorizer. I learn as I work and work as I learn. Being expected to solve algorithm puzzles on the spot feels as unrealistic as it is stressful. Yet, even when I managed to ace one round, there was always another—and another—until eventually they determined I was “not experienced enough.”

That’s when I realized I needed a different approach.

From Stuck to Spark

For all the problem-solving I love, I’ve never considered myself creative. I’ve always been better at running with ideas than coming up with them. So when people suggested, “Why not build your own projects while you job hunt?” I didn’t know where to start.

Deciding what to build felt like the hardest part. Until one day, something clicked. An idea came to mind. Then another. And another. For the first time in months, I felt a spark of momentum. The ideas were coming faster than I felt I could build them, and that's when the idea for CodeQuest118 hit me:

What if I committed to building 118 projects—not just to sharpen my skills, but to document my journey, share what I learn, and (hopefully) inspire others?

Why 118, you ask? Honestly, it’s just a number I’ve always liked. My lucky number, you could say.

What to Expect from CodeQuest118

Through this blog, I’ll be sharing every step of my journey. Here’s what you can expect:

  • Project breakdowns: What I built, why I built it, and the mistakes I made along the way.
  • Lessons learned: Tips and insights from tackling real-world challenges.
  • Inspiration: Ideas for your own coding projects, whether you’re just starting out or leveling up.
  • Personal growth: Reflections on the ups and downs of learning, failing, and improving.

My hope is that this blog will be a resource for anyone navigating their own coding journey—or just looking for a little inspiration to get them started.

Join Me on the Journey

Will anyone read this? There’s no way to know. But even if it’s just for me, CodeQuest118 will be a record of how far I’ve come—proof that my skills are more than the value employers place on them and a space to show what’s possible when you commit to learning.

If you’ve ever struggled with tech interviews, felt stuck in your job hunt, or wondered what to build next, you’re in the right place. Follow my story, explore new ideas, and share your thoughts along the way.

What’s the biggest challenge you’ve faced in your coding journey? Let me know in the comments—I’d love to hear your story!

Labels:

Comments

Post a Comment

Popular posts from this blog

Submitting My First Chrome Extension

 What I learned Along the Way I’m excited to share that I’ve officially submitted my very first Chrome extension for review! It’s a free tool designed to help simplify Google searches. Now, I know what you’re thinking—can Google searches really get any easier? And my answer... well, for me at least, the answer is yes. I have this weird habit when it comes to searching for information, one that involves a repetitive action. I recently realized that noticing repetition is a powerful way to discover new projects. I know I’m being vague here, but trust me—stay tuned! Once the extension is officially live on the Chrome Store, I’ll be sharing the full post detailing what I’ve built; it's a simple yet useful tool! The Process of Publishing an Extension on the Chrome Store Let’s talk about the process of publishing an extension. Honestly, I was surprised at how straightforward it was. Here’s what you’ll need to get started: A compressed file containing your manifest, JavaScript files, and ...
Post a Comment
Read more

Perfection Paralysis

You can't edit a blank page. - Jodi Picoult   So, it’s been a while since I’ve posted. Truthfully, I’ve hit a bit of a stall in my development. Here’s to hoping that writing this post helps me work through the funk! I’ve been working on a relatively large project. Actually, it’s technically two projects rolled into one. When I finish, I might even claim I’ve completed two separate projects. Is that cheating? Maybe. But who’s counting? If you’ve been following along, you might notice a theme here: just like HIITGenius.com , this project ties back to my part-time job as a gymnastics coach. I promise not all my projects will have a gymnastics connection! But when you think about it, it makes sense. Projects are often born out of your day-to-day life—the things you know, see, and ultimately decide you can improve upon. At my job, we track our hours the old-fashioned way: pen, and paper. It’s not fancy, but it’s been working for over a decade. That said, I know it could be better. So,...
Post a Comment
Read more