This is an automated archive made by the Lemmit Bot.
The original was posted on /r/godot by /u/overthemountain on 2025-01-23 01:25:48+00:00.
I've been working on some Godot projects mainly for fun. I'll get stuck and try and few things, but when I'm kind of at a dead end, I'll come to post on here. I'll write up a detailed explanation, and often, in doing so I'll figure out the solution.
This is the third or fourth time I've done this in the past few weeks, so I thought I'd write something about that.
I've been a developer for a while now (over 15 years). Not a game developer, just a normal software dev working in tech. I actually do product management now, but that's besides the point. I know a lot of people here are very new to coding in general. I see a lot of people posting bugs that are often very obvious to solve at first glance. You forgot "var" or mispelled a function name or didn't use onready or something like that.
Learn to really detail what is happening. Explain what you are trying to do, what you've tried to resolve the issue, and where you think the problem might be. Often when I do this, it makes me realize I haven't checked one thing or another, and often, one of those things is the solution.
I'm not saying you can't ask questions here, I have posted a few I wasn't able to resolve right away myself. If you want to be a developer (game or otherwise) I think it's an important skill to learn how to debug your code. There won't always be an AI or another person in a forum or Discord to help you. Besides, it takes time waiting for responses.
Write as much detail as you can. Try to think of what other people are going to ask or suggest. Make sure you've already tried all of those things. If you're really new you might not be able to think of many things, but as you go there will be more and more things you'll be aware of.
While I've never seen it anywhere I've worked, I've heard of people talking to a stuffed animal and explaining the problem before going to other people, and often discovering the solution by doing so. You'd be surprised how collecting your thoughts and putting them down on paper or speaking them out loud can help you think of things you might have skipped over.
Give it a try and good luck.
For reference, here's the problem I was trying to solve - well, here's a before and an after, I'll let you guess what the problem was and how I solved it.
Before - something is broken
After - problem solved