My day job is writing software for embedded systems, and I strongly discourage choosing C as your first language. It’s very unfriendly to novices and - depending on your OS - even getting anything to compile might be a challenge in its own right.
That said, the most fundamental thing about programming is finding solutions to problems. Languages are tools you can use to solve your problem, but your tools cannot do the thinking for you. In that regard it’s immaterial what you start with; you will eventually gain problem-solving experience that translates well to any tool you use.
The Godot documentation contains two example projects (Dodge The Creeps and Squash The Creeps) that, personally, I find very accessible. They’re both light on code and do something very clever that they never tell the reader about: they teach about how to solve problems using composition. Godot uses something called ‘nodes’, which are little specialized tidbits of functionality that you can mix-and-match to form just about anything you want by adding just a little bit of ‘glue’ code. If you can reason about which nodes will be useful in solving a problem, you’re already well on your way to a solution.
Definitely don’t be afraid to ask a well-structured question. It doesn’t cost anything, and most people are willing to help. In fact, if you know somebody else who is developing in Godot, consider sending them code you already wrote and ask for feedback on how to make it better. This is called a ‘code review’, and it’s something software teams do. If you’re contributing code to a project, it’s usually standard procedure to make a ‘pull request’. People will look at what you wrote and provide suggested changes on how to make it better, and the best reviewers will even tell you why. This is by far the best method of learning the finer points of the trade.
I’m not big on video tutorials. Most of what’s on YouTube is made by people with great intentions, but I find that most videos focus on outcome over process. Most videos will tell you when to connect a signal and how to instance a scene, but never explain why you’d want to do any of those things. Anyone following along will end up with a perfect usable title screen or wall jump mechanic, but without actually learning anything.
If you’re looking for general books on programming, I can recommend The C# Yellow Book by Rob Miles. Although C# is a phenomenal language that isn’t too hard to pick up for a complete newcomer (it was my first real language) and is also supported as a scripting language in Godot, neither of those are the fundamental reason I recommend the book. It’s because the book teaches from first principles, is a fairly short read that doesn’t drone on about inane minutiae, and uses approachable and non-scholarly language. (Coincidentally, if you pick C as your first language and look for a book on it, there’s a very real chance you’ll end up buying K&R’s C-programming book, which is the inverse of all of those qualities. Another reason to not pick C. Please value your sanity and choose anything else. It’s already too late for me aaaargh~~~)
’
