Post History

# It's the opposite of code golf.

Code bowling is essentially a challenge where you try to write the *longest* code possible, as opposed to the shortest code. Now, this format comes with many issues, and you may be able to see why. For example, just adding comments increases code length - you need a _very well-defined, specific, strict_ set of rules to write code-bowling challenges. It's very tricky to do this well - most code-bowling challenges on Stack Exchange failed to meet this, and as a result were later closed and locked. 

A good place to start is the rule "any removals from the source code make the code not work anymore", but this is not really enough to stop the endless possibilities of loopholes to make your code longer.