Spot on ... I'm guilty of all 5 points, to one degree or another. As soon as a project gets to be hard and just feels like work, i have a bad habit of bailing and moving on to something more "fun" ... which eventually turns into hard work!!
Nice stuff, the second reason applies to all types of skills instead of only gamedev. I feel the fourth one isn't completely a lie but less of they "cant do it" and more of "you are going to take 4 to 5 times more than the other one". I feel personally attacked by the fifth one :/
I hope in the six months since you've made this video, you've realized how bad some of these points are. Holy moly point 4 is an absolute disaster. People call me pessimistic but christ, put some light in your life.
If you don't like my video then create your own video about the 5 reasons most people never finish creating their first video game and post it for the world to see. You're obviously an expert since you have posted one 14 second video on your UA-cam channel.
@@computerhobbyists3070 Yeah, I really didn't like the video and it got on my nerve quite a bit. Probably shouldn't've made an unhelpful comment hating on it so sorry about that. That said, I'm not looking to have a pointless argument so I'll explain myself better. Point 1, No problem there. Start small, start simple. Build up your skills with each game you make. Technically, you could make a bigger game first try, but that's not for everyone. I think the main point is to just to have fun, enjoy what you're making and to not get stressed or pile too many things on at once. Point 2, Once again, mostly not a problem. I think it's the fact that you make it sound like your point is absolute. Forcing yourself to work through a game can be good for some people, for others it just makes them despise working on it after a while. There's a difference between breaks and losing interest. If your losing interest, brute force doesn't always work. Point 3, Books, tutorials, whatever it is, who cares. It's all good. The point is how you learn. If you pick up a book and start going through variables, lists, interfaces etc without even applying/understanding it, then it's just as useless as a tutorial online. 1# for learning to program is problem solving. You run into a problem, you break it down into steps and you figure out how to solve each step. Solving the step, however you find the information, is what helps things stick. Learning stuff before knowing why you need it is like finding the key before the locked door in a puzzle. Point 4, basically sounds like you're saying to avoid what you're not good at and to not bother even trying because you're not 'inclined' towards it. I get the idea that there's only so much time in the world and you can't master everything. However, there's a balance with how much time you have available and how you spread it across your skills. Some skills may take much longer to pick up but if you have the time, why not pick it up? Point 5, Eh. I don't even know what to say about it. A person knows themselves best. It's more about just being honest with yourself, knowing why you give up and working to fix it. I'd say working on a game could be a good way to work through it. Though, 'Discipline' implies you're just forcing yourself and not really working out your issues. These points are vague enough to work as a general approach to life. I think I mostly agree with your points but it's your harsh and 'tough-luck' attitude that really doesn't help with the way you word your points. This is less a video for beginners and more a video for people who don't care to finish their game. Even for those people, I don't think these points really help unless your trying to guilt them or make them feel shit for not finishing anything. Overall, just rubs me wrong way.
Spot on ... I'm guilty of all 5 points, to one degree or another. As soon as a project gets to be hard and just feels like work, i have a bad habit of bailing and moving on to something more "fun" ... which eventually turns into hard work!!
Nice stuff, the second reason applies to all types of skills instead of only gamedev. I feel the fourth one isn't completely a lie but less of they "cant do it" and more of "you are going to take 4 to 5 times more than the other one". I feel personally attacked by the fifth one :/
I hope in the six months since you've made this video, you've realized how bad some of these points are. Holy moly point 4 is an absolute disaster. People call me pessimistic but christ, put some light in your life.
If you don't like my video then create your own video about the 5 reasons most people never finish creating their first video game and post it for the world to see. You're obviously an expert since you have posted one 14 second video on your UA-cam channel.
@@computerhobbyists3070 Yeah, I really didn't like the video and it got on my nerve quite a bit. Probably shouldn't've made an unhelpful comment hating on it so sorry about that. That said, I'm not looking to have a pointless argument so I'll explain myself better.
Point 1, No problem there. Start small, start simple. Build up your skills with each game you make. Technically, you could make a bigger game first try, but that's not for everyone. I think the main point is to just to have fun, enjoy what you're making and to not get stressed or pile too many things on at once.
Point 2, Once again, mostly not a problem. I think it's the fact that you make it sound like your point is absolute. Forcing yourself to work through a game can be good for some people, for others it just makes them despise working on it after a while. There's a difference between breaks and losing interest. If your losing interest, brute force doesn't always work.
Point 3, Books, tutorials, whatever it is, who cares. It's all good. The point is how you learn. If you pick up a book and start going through variables, lists, interfaces etc without even applying/understanding it, then it's just as useless as a tutorial online. 1# for learning to program is problem solving. You run into a problem, you break it down into steps and you figure out how to solve each step. Solving the step, however you find the information, is what helps things stick. Learning stuff before knowing why you need it is like finding the key before the locked door in a puzzle.
Point 4, basically sounds like you're saying to avoid what you're not good at and to not bother even trying because you're not 'inclined' towards it. I get the idea that there's only so much time in the world and you can't master everything. However, there's a balance with how much time you have available and how you spread it across your skills. Some skills may take much longer to pick up but if you have the time, why not pick it up?
Point 5, Eh. I don't even know what to say about it. A person knows themselves best. It's more about just being honest with yourself, knowing why you give up and working to fix it. I'd say working on a game could be a good way to work through it. Though, 'Discipline' implies you're just forcing yourself and not really working out your issues. These points are vague enough to work as a general approach to life.
I think I mostly agree with your points but it's your harsh and 'tough-luck' attitude that really doesn't help with the way you word your points. This is less a video for beginners and more a video for people who don't care to finish their game. Even for those people, I don't think these points really help unless your trying to guilt them or make them feel shit for not finishing anything. Overall, just rubs me wrong way.