I have never found any language that is self documenting I once worked for a major company in the pro audio busness that had that maxim. I wasted days and possibly weeks trying to get things working becuse there was no software desingn stratergy documentation and poor comments. That sofware was (is?) written is pascall.
I will chuck my words in the debate about code standards:
Make subroutine/function/procedure names desciptive but short witout being too criptic
Comment each line of assembler exept where it would be banal
Place a short decription of operation of each subroutine/function/procedure above the code and (abridged version) in "extern" lists
The main loop should be an understandable series of calls use only necessary code at this level
Use of upper and lower case should be consistent and helpfull
The acid test is to maintain code ten years old and no wonder what you where taking when you wrote it