DEV Community

Discussion on: What It Actually Feels Like to Build Something You're Proud Of

Collapse
 
codingwithjiro profile image
Elmar Chavez

You clearly described what I went through when first starting out. Earlier in my career transition to tech, when I only know vanilla HTML, CSS, and JavaScript, I had this idea of creating an interactive tarot card reader inspired from freeCodeCamp's lab exercise. It reads a person's past, present, and future randomly.

It was an idea born from being frustrated of not having a site that does exactly that. So I decided to just build it myself. At first it was tough, had to scrape for an API for my card data and card images but ultimately I finished it in about one month with less than a year of experience.

After deploying, I honestly felt like it wasn't enough and it doesn't hold up to my standards. I just told myself that it is done and just let it be. There are multiple bugs when I tried to spam click cards, mobile responsiveness are jagged sometimes, but I just said at least I finished what I started.

However, as I create more projects, I still look back at this one and can't help myself to be proud of something that I wasn't sure I was going to deploy in the first place. Even though it has more bugs, it has a huge index.js, and a wonky CSS, I'm still proud to call it mine.

Today, this is my most starred and most consistently viewed and cloned repo. Now imagine if I discontinued this, I would have zero chance of sharing my idea to the world.

Live Link: veil-and-visions-fcc-jiro.netlify....
GitHub Repo: github.com/CodingWithJiro/freecode...