pouyathe

You've pinpointed the exact issue - it's option (b). I developed a personal style coding in isolation and didn't learn conventional formatting. The "else if on separate lines" pattern became a habit that snowballed into that brace nesting.

I'm fixing it now. You're absolutely right that it will be much more maintainable.

The "brilliant 17 year old" comment means a lot. I'm learning that part of brilliance is knowing when to follow established patterns. Thank you for the mentorship through critique.

The cleanup starts today.

Thank you for the book recommendation. I've just downloaded "Crafting Interpreters" and will study it properly. I've been coding in isolation (due to circumstances I can't easily explain), so learning from established resources like this is exactly what I need.

The messiness comes from years of solo experimentation without mentorship. I'm now committed to cleaning it up using proper techniques.

I appreciate both the kind words and the tough love.

Honestly, my code is like my school notes. Even my teachers can't read my notes during exams! They always say: "The answers are right, but the handwriting... ah!"

I'll make it better.

I'm currently working on the documentation and I'm close to finishing it. I've been putting real effort into this and hope to have it completed soon.

Best, Pouya (A 17-year-old Afghan teenager from Iran)

    "Update: Wow, this got a second life! Seeing a spike in GitHub clones (328+ in 2 days). If anyone's trying G, I'd love to hear:

        What's your use case?

        What's the biggest hurdle you faced?

        What feature would make G actually useful for you?

    Thanks for checking it out! — A 17yo student building this."