Inverse Law of Gamejam Code Quality

I love how my quality of code for these game jams works on an inverse principle.

Ludum Dare hour 0: "Well, let's stick to SOLID principles, abstract and document all interfaces, and make sure it's very nice clean code."

Ludum Dare hour -0.15 to deadline: Writes pointer accesses to directly muck with bits inside private structures of another object "I don't care, nobody will ever maintain this code..."

Ludum Dare in the future, with a new platform/post-compo release: "OH CRAP."