What goes wrong when I try to ask a question

[Chekhov]

Every time when I try to figure out some programming problem or issue with ren'py or python itself, I eventually have to articulate a question to explain what I'm trying to do and how I'm trying to achieve it. I have to list all relevant code. To be honest it's quite a hassle. When I program in something new (in this case ren'py) there is an additional learning curve. I still don't really understand how initialization of objects is supposed to work for example. But it gets worse; that also means you have to register a new forum account, learn the forum rules to avoid stepping on toes....


....and then when you've done all that and laid out the problem, the solution just stares you in the face.

This seems to happen on a weekly basis for whatever thing I'm trying to learn and I felt like venting this. Also, I'm new on this forum. Hi everybody. Don't you just hate how your own lack of focus/organization is sometimes the main problem with programming?

Can I get anyone a beer? Next round on me.

[BunnyAdvocate]

This is why there's a term in programming called rubber duck debugging, where you basically explain your programming problem to an inanimate object, and in the process of doing so, recognise the reason for the problem. It's a pretty common feeling~

[Imperf3kt]

I've done this several times.
Worst is when its a specific hardware issue and you've detailed everything to the most minute detail, only to test it on different hardware and realise it was the computer itself, that is the issue.

Old hardware

[Chekhov]

Rubber Ducking. He he, that's a pretty funny way to conceptualize it.

Though the hardware issue seems particularly bothersome. I suppose it's part of the process of getting things to work.

Is this the official renpy forum by the way or simply one of the bigger ones?

[Imperf3kt]

This would be the official forum.