DEV Community

Shreelaxmi Hegde
Shreelaxmi Hegde

Posted on

Cloning a website taught me more than tutorials did.

I recently completed a CSS tutorial. As a part of the tutorial i built this project with the guidance of a wonderful teacher.
I applied what I learned by building a clone of a well-known music app Spotify. I focused on recreating its dashboard page using HTML and pure CSS.

Spotify clone project preview

Even though the project doesn't have advanced functionality or interactive features yet, the journey taught me more than I expected. It was a valuable experience that made me realize something important:

I should stop only watching tutorials and blindly copying code. Instead, I need to apply what I learn to real-world problems.

Yes,
It hit me hard.

Whenever you learn something from a tutorial, take a moment to ask yourself:

Where have I seen this concept used before?
How can I apply it to something I'm building or interested in?


  • In web development, there are no hidden secrets. You can see everything on a website if you inspect it carefully. Most great websites start with the basics: HTML and CSS. So, the next time you see a well-designed website, pause and think:

How was this layout built?
Is this using Flexbox? Maybe this square element has a 270-degree rotation with a transition.

This type of thinking builds creativity. Great designs are often a combination of many small and thoughtful details.


  • Don’t blindly code. Break down the entire layout into smaller parts. Complete each task. One step at a time.

  • Use browser DevTools effectively. They're very helpful for testing, debugging, and previewing changes. Avoid switching tabs multiple times for simple things. Use devtools instead.

For example, in this clone, I found that a CSS property wasn’t applying as expected. Using DevTools, I discovered another rule was overriding it and quickly fixed the issue.
Testing flex box logics, sizing elements, animations, effects etc. become smooth with this.


  • Building real projects always unlocks new insights, tips, and tricks. You get to know what it feels like to be a real developer. When you run into bugs don’t run away. Face them. When you want to add a feature you haven’t learned yet, go learn it and build it. Never be lazy to explore new things. That’s how strong foundation built.

Final Thought:
Learning through real-world practice creates a deep understanding that no tutorial alone can provide. Keep building. Keep exploring. That’s the path to becoming a great developer.
You are building a new thing. Give it a life. Put your curiosity, passion, whatever it takes.
Stressed out? take a small break, continue.
Embrace all the obstacles you face.
Learn from every mistake. Enjoy the process.
Don't forget why you started the journey.
Happy Coding.


Let me know what you think.
Happy to hear a valuable feedback from you.
If you have a nice feature to add on or want to collaborate feel free to reach out. You are always welcomed.
Or you want me to contribute to your one of the works I'm open 🙌.

Checkout the project on github.

Top comments (5)

Collapse
 
xwero profile image
david duymelinck

I think it is a path others should follow.
it is not the easiest path, but because you have to think about all the parts you learn how to build on top of other parts.

I'm wondering, did you make a plan before you started?

Collapse
 
dshree profile image
Shreelaxmi Hegde

Thank you! 😊
I totally agree. It's not the easiest path.
Thinking through every path of the build with the confusion of

what property to use why it's not working balancing the original site with ours etc. is frustrating and annoying.

It takes a long time just to create simple feature at the beginning. Each bug says _to give up you can't do it. _
But after it all the will to build on our own, curiousity to learn that one new feature give enough fuel to keep going. It is the most rewarding path.

As I mentioned on blog ,

As a part of the tutorial i built this project with the guidance of a wonderful teacher.

Before watching the lecture, I tried to build on my own and then compared what lecturer suggested.

I roughly sketched the whole layout by breaking big sections like sidebar, main intent area and the music player part. And then started to build one part at a time.

Collapse
 
xwero profile image
david duymelinck

I roughly sketched the whole layout by breaking big sections like sidebar, main intent area and the music player part.

Those are still big parts, I suggest you create smaller parts.

Thread Thread
 
dshree profile image
Shreelaxmi Hegde

Yep.
Thank you 😊

Some comments may only be visible to logged-in visitors. Sign in to view all comments.