Feeling stuck and Suffering from Shiny Object Syndrome
Posted by Zestyclose-Window358@reddit | learnprogramming | View on Reddit | 12 comments
Hello Everyone Teen Programmer here,im Currently feeling really Stuck right now and Demotivated
basically i choosed a Project that was way out of my Scope and League: A Game Engine
this was a horrible Project Idea especially because ive never made a video Game before,never used a Game engine before,and am still relatively new to Programming
and due to all of this,im really confused as to what problem to Solve or what to make since everything seems too Abstract for me,ive been using OpenGL as the Graphics API for this Project and my entire journey has just been learning about an outdated and shitty State machine of an API.
this really seems like a Problem with me and wanting to quit when Progress seems to plateau,but i also dont want to quit because of sunk Cost fallacy,would quitting now be a strategic Pivot or just Giving up when you are stuck?
light_switchy@reddit
Old does not always mean bad. On the contrary old can mean well-supported, mature, and well understood. OpenGL is just fine.
A simple compiler is significantly smaller in scope than a simple game engine. But what you should do is make some simple games. Forget the engine. Just make games. You dont need to use an existing engine if the technology is interesting to you.
There is an old article entitled "Make Games, not Engines" that covers just some of the reasons that this is the way to go.
Zestyclose-Window358@reddit (OP)
Yea,i am planning of making a simple ping pong game in OpenGL now which seems much more realistic than a full blown game emgine
light_switchy@reddit
FYI I fixed the link to the article if you're interested
PalpitationOk839@reddit
This is very normal you are not stuck you just chose a project that is too big for your current level building a game engine or compiler is very advanced you should switch to smaller projects like simple games or apps and build up gradually that is how progress happens
Naive_Cardiologist_6@reddit
make a PRD. then make an MVP. then make action items. then implement and test. then make it shiny. then give access to your friends for testing. then deploy.
debirdiev@reddit
Why quit? Put it to the side for a while and work on other projects and come back to it later. "Quitting" a project like this isn't necessarily quitting. You can always swing back around to it. No need to bang your head against a wall without trying to get around it
TheNewJoesus@reddit
You should try a more light weight game engine first. Definitely stick to 2D if possible. I recommend checking out PICO-8.
Building a compiler is a difficult projects. We had a class in university on how to build a compiler, and it definitely took the entire semester for me to understand and comprehend.
Also, be okay stopping a project halfway. Do the same project 5 times if you want. Make bad things.
cgoldberg@reddit
Start small with reasonable beginner projects... building a game engine or compiler when you don't really know how to program is nowhere near realistic. You will definitely fail and be unmotivated. Choose something feasible.
Zestyclose-Window358@reddit (OP)
I think it was my ego actually like Wanting to build something more "difficult" than what others are building just to feel superior.but im much more wiser now
cgoldberg@reddit
You really don't sound wiser at all. You are posting about the problem and stating you want to write a compiler. Nobody is going to care or think you are "superior" because you built a difficult project. If you actually want to learn, start small and be realistic with your skills and capabilities.
Zestyclose-Window358@reddit (OP)
I was being Sarcastic when i Said that,Sorry.
YesterdayOk921@reddit
You should break the project into parts and subparts and then try to build or fix that feature alone. Do not jump straight into the full project.
If you want you can switch to a new project but you should commit yourself to it and not hop onto another one. Just try to build it in small pieces.
Consistency is the key.