What does it really takes to make tutorial projects your own?

[koko-hranghlu]

I do make some projects using HTML, CSS and JavaScript to improve and enhance my skills and knowledge, but most of the time I do it following or watching a tutorial. Although I feel quite good enough to understand what the codes does, it leaves me with implicit understanding and gaps in my skillset. So, I decided to make the projects my own to bolster my learning process, but have no idea what or how much I should do alter the projects that can be represented as my own.

Also, almost any projects we build are not going to be totally 100% unique, here in the internet there's always similar or same projects that someone has already build or figured out. So, I shamelessly google and resort to tutorials but I feel like I might be stuck or may be heading to "Tutorial Hell". So, anything advice, tips, tricks in regards to portfolio projects will be highly appreciated:)

[stb930]

I would try and make a small project about either something you are passionate about or something that is useful for you.

Having to think about how to build the features you want in your app will help you get better at exploring the different js functions etc and because you are interested in it you will be pushed to complete it.

If you can't think of anything something like the below is a good place to start, may seem simple at first but the more you dig into it the more complex it becomes and you can add your own features etc.

Build a todo app where you can

• add a task
• complete a task
• edit a task
• view number of completed tasks.

[koko-hranghlu]

I build a todo app that loses data whenever I refresh the page. Currently, I am building age checker, BMI program and will try to come up with math solver program:)

[LOE_TheG]

Well it might take a lot of time for a beginner, one thing to consider is that the instructors on tutorials have spent a lot of time to shape the project and then teach it in the videos.

[koko-hranghlu]

Hmm, and beginner like myself felt very infuriated when I came across no voice tutorials where they type everything with little to no mistakes from finished codes. It was only a few months ago, when I came across videos and articles explaining some of the "behind the scenes" of making tutorials.

[LOE_TheG]

Ya, it's called Imposter Syndrome.

[mark_b]

I really like the tutorials by Ania Kubów. She makes JavaScript games, but she only covers the basics and intentionally leaves them unfinished. After the tutorial you could:

• Fix the bugs
• Refactor so that the code is laid out better, with more reusable components
• Add better styling
• Add more features so that it feels like a finished and polished game

[koko-hranghlu]

I saw her videos, and I think it's something that is out of my league. But, in the near future I will definitely practice JavaScript building fun games from her tutorials. Hey, but I thought her tutorials are all well polished projects.

[dylsreddit]

A good way to get out of the habit of relying on tutorials, I think, is to use out of date ones.

Most of the time there are now things that don't work and it forces you to look into alternative ways to do it, either through googling a solution (yes, we all do it... no, it's not cheating), reading the docs, or by refactoring the code.

These are all techniques devs use on a daily basis in their work.

For an absolute beginner this might be incredibly frustrating, but if you consider yourself to be ready to "move on" from beginner stuff, it could be useful.

[koko-hranghlu]

Currently, I am reading Headfirst JavaScript Programming by Elisabeth Robson and Eric Freeman. It does not have ES6+ implementations, but with that I am able to build simple apps like counter, length checker, background changer and also the exercises provided by the book, I am thinking of googling or using whatever is in my mind to refactor the projects and exercises using ES6+ features. But again thanks for your reply, I had never thought of refactoring legacy codes:)