It's your code, no one else will ever see it or maintain it. What worst practices and cheap shortcuts do you use when you really are going "quick and dirty?"
Ask HN: What horrible things do you do in your own code when no one is watching?
1–10 of 40 posts
Re: Ask HN: What horrible things do you do in your own code when no one is watching?
#2Global variables... I'm ashamed.
Re: Ask HN: What horrible things do you do in your own code when no one is watching?
#3Single letter variable names.
Re: Ask HN: What horrible things do you do in your own code when no one is watching?
#4No tests. At all. Ever.
Re: Ask HN: What horrible things do you do in your own code when no one is watching?
#5Single letter variable names.
and reuse of them!
Re: Ask HN: What horrible things do you do in your own code when no one is watching?
#6Skipping tests...
Re: Ask HN: What horrible things do you do in your own code when no one is watching?
#7I do all of these things in the same block of code.
Somebody off me.
Re: Ask HN: What horrible things do you do in your own code when no one is watching?
#8Premature optimization.
Cause it's fun.
Re: Ask HN: What horrible things do you do in your own code when no one is watching?
#9Hard code passwords and temporary filenames.
Re: Ask HN: What horrible things do you do in your own code when no one is watching?
#10Ditch optparse or argparse -- "flag = '--flag' in sys.argv" or "if len(sys.argv) > 1: arg = sys.argv[1]" will usually do...