There's some good advice in these comments, particularly Manuel Meyer's - code should mostly be self-documenting, i.e. you should be able to tell what it does by looking at it through naming and attention to semantics. For a beginner to do this is quite hard but it will come with time.

However it seems to me that your problem really is that you had too many changes in flight and no/limited ability to walk them back. What you need here is version control and regular commits so that if you start doing something and it doesn't work out, you can bin it and go back to the stable version. Effectively at the moment you are flying without being a fully trained pilot, and you've not brought a parachute, so of course it ends badly.