Blatantly obvious bugs and well-known bad practices every few lines. You can't ever trust the code without rewriting it function by function. Second place: A

Blatantly obvious bugs and well-known bad practices every few lines. You can't ever trust the code without rewriting it function by function. Second place: All territory, no map. Is there a design document? An architecture description? Comments that tell why, not just what? If a new person starts work on the code, do they have to step through it to figure out what's going on, or is there a map, signposts, and a guidebook?