In here I'm doing the same thing as Hourences in his book and commenting on my own maps. I try to decompose each of my own maps into smaller pieces and take the time to analyse the decisions made during the process to make the maps. This process, to analyse one's own work, lead me to some enlightenment. To be able to talk about problems you must also know the solutions. As Mark Rosewater teaches in his design lessons, your audience is good at identifying problems but not so much in solving them. To able to see the problem is required, but to be able to move past them is in another league of skills.
An important detail: I didn't write the comments right after finishing the map. There is a gap of many (5+) years between making the map and writing the analysis, mind you.
Dowload from: moddb (Unreal Tournament maps) | Unreal archive | Mapraider (open arena)