My point is that beginners should not look at tutorials as being the end product, but a way to get to the end product. I am very thankful for my MPG calculator i made my first week of college. It got me to the second week of college. There were times early on that when I wanted to make a simple little program to do something dumb like take a number someone gave me and do something entirely different with it, i often had to look at my MPG calculator to remember how i implemented certain concepts.
What I see with people who post in the way i'm referring to their To do app or their calculator is that they don't know the concept they just implemented, or what that could get them in the future. and these are mainly hobbyists anyway. Thus, the best way to learn as a hobbyist? Make something that helps you. You'll learn far more in setting out to make something that solves your own problem than by solving a problem that's been solved already by everyone. Often in solving your own problem you have to reference the tutorials that do explain how to create a todo list app. but if you go to it not knowing what you want to do when you're done, all you'll have is a todo list app. if you go to it knowing you want to implement a list system in X language, you'll leave most likely knowing how to implement a list system in X language.
I'm pointing out a fundamental problem with tutorials, not necessarily a problem with those who do them.
It's clear it's become a bigger problem than just tutorials as well. Because you have people who are more skilled, have had years of experience, and they're doing the same thing with covid trackers. It takes a little bit more skill to do so, but it's the same underlying problem: lack of know how to create original ideas.
I don't discount tutorials, I discount how we use them.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My point is that beginners should not look at tutorials as being the end product, but a way to get to the end product. I am very thankful for my MPG calculator i made my first week of college. It got me to the second week of college. There were times early on that when I wanted to make a simple little program to do something dumb like take a number someone gave me and do something entirely different with it, i often had to look at my MPG calculator to remember how i implemented certain concepts.
What I see with people who post in the way i'm referring to their To do app or their calculator is that they don't know the concept they just implemented, or what that could get them in the future. and these are mainly hobbyists anyway. Thus, the best way to learn as a hobbyist? Make something that helps you. You'll learn far more in setting out to make something that solves your own problem than by solving a problem that's been solved already by everyone. Often in solving your own problem you have to reference the tutorials that do explain how to create a todo list app. but if you go to it not knowing what you want to do when you're done, all you'll have is a todo list app. if you go to it knowing you want to implement a list system in X language, you'll leave most likely knowing how to implement a list system in X language.
I'm pointing out a fundamental problem with tutorials, not necessarily a problem with those who do them.
It's clear it's become a bigger problem than just tutorials as well. Because you have people who are more skilled, have had years of experience, and they're doing the same thing with covid trackers. It takes a little bit more skill to do so, but it's the same underlying problem: lack of know how to create original ideas.
I don't discount tutorials, I discount how we use them.