This is an automated archive made by the Lemmit Bot.
The original was posted on /r/godot by /u/Buttons840 on 2024-10-05 05:52:17+00:00.
I've done a lot of small project to learn different node types and other technical aspects of Godot. I was starting to feel like I knew all the tools and pieces I needed to assemble a game, but I was still unsure how to architect a game.
I took a Godot course / tutorial on Udemy, and some of it was insightful, but also the course instructor was making a lot of really weird architecture decisions I didn't agree with. Some of them actually made me upset because I considered them so bad.
But what surprised me is, if I followed the course and just did the things I disagreed with, thing turned out fine and the code was still easy enough to work with.
In the end I learned a few different architecture option, and although I personally wont use some of the architectures the instructor did, I also learned that it doesn't matter.
The most important lesson I learned was that just moving forward with a poor architecture usually works well enough and I need to stop obsessing over architecture so much. There's lot of options that are good enough.