Imagine a project of 6k lines of this and the migraine it would cause, even if its faster. Also, comments are always a good idea whenever clever code is employed.
I can imagine; I just printed out the source to The Penguin 77's Tetris Marathon (64 pages) and Quigibo's Puyopuyo (49 pages) in an attempt to learn Asm.
You printed 113 pages of asm code!
That's dedication!
Readability is really important, er... at least it is for normal sized projects, obviously not for simple assignments. Often you finish one part of the code then start working on another only to find later you have to change that original section of code, only now you forgot what you did! Its necessary to leave clues about what everything does becasue even though you wrote everything, its very very easy to forget. Especially in assembly you have to keep track of more than just what it does, you also have to know if things need to be called or jumped to, what registers are needed for input and output, which registers get destroyed and which ones are preserved, the state of the stack before and after, etc.
Axe right now is 6770 lines of code for instance, which is over 100 pages if printed. One way I keep it organized is by overusing macros. You should see some sections of code are entirely macros to make it more readable. I'll attach a screen shot to show you what I mean. You wouldn't even be able to tell that its asm:
