"Never do in code what you can get the SQL server to do well for you" - Is this a recipe for a bad design?
"A [answer|question] you recently down voted has been revised by its author."
Is it actually possible to have a 'useful' programming language that isn't Turing complete?
Matching the same word twice with a regular expression, not caring what the word is
Verifying that a user acknowledges and understands a given message without adding excess inconvenience
Deliberately annoying users to discourage certain behaviour. Is this a bad idea?
A single, long load - or multiple short loads, which would provide a better experience?