Have you ever got to the point where your code get so complicated you can't work on it anymore ?
What do you do in this case ?
>>59972720
Ask yourself how it got to be so complicated. Poor choice of architecture, lack of understanding around the problem domain, no documentation, etc.
Then start over and use the lessons learnt to make something better.
>>59972720
At that point I have self loathing moment for being so self-taught and not learning the boring stuff like organizing code clearly.
>>59972720
take a step back, mentally visualize your structure, and document your original thoughts.
use the documentation as a form of a checklist and review your code.
>>59972720
You should have been using design patterns from the start
1. Review what problem you are trying to solve with the code
2. Compare current solution does it versus how you would do it knowing what you know now
3. Plan some steps to move towards the "better-informed" structure
4. Apply steps
5. Repeat
With each iteration of review, your code will improve and become clearer.
>>59972720
Consult the comments you added.
/thread
>>59974888
>comments
>good code
>>59974975
Yes.Good code and good comments are a necessity.
>>59975039
What I meant is that if you have to heavily relay on comments then your code is bad.
You fucked up bigly. Architecture should be planned from the get go. If you have to use a non oop language then kys it will always be a sticky mess.