Hehe, I have no idea who wrote it. To be honest it looks like someone just trying to get stuff done asap who's working alone and at worst it's a bit old fashioned, if functional. It's generally quite clear, it's compact and direct and it's not confusing or spaghetti-fied. But there's on element onclick js binding, inline stylesheets, inline javascript, poor scoping on variables, lots and lots of commented out code.
The commentated out code is a personal bug bear of mine. I'm always reminding junior programmers to delete commented out code from the system, I tell them they should never check in commented out code and that's what source control is for. It's a simplistic explanation to deter discussion, in reality it's because of YAGNI and that personally it always dis-orientates me and slows me down while I'm working on code. I get distracted by trying to figure out why it's there and usually it's out of date and within a year it will still be there but now refers to functions that have been entirely removed.
Commented out code becomes stale very quickly. People fear to remove it because they think it must have a purpose, when it rarely does. It becomes unnecessary noise and the person who was best placed to delete it is the one who commented it out in the first place.
I think it's a bad coding habit that you have to consciously break at some point, I certainly used to do it.