News for hackers. Stuff that matters.
Re:When To Write Bad Code by alexkus on Tuesday January 29, 2013 @11:23AM (#5134785)
Write prototypes in a language that you don't use in production.

It allows you to get to grips with the problem and prevents you from just copy-and-pasting large chunks of the "i'll rewrite this later" code into production.

I tend to write my prototypes in Perl as I used to use it a lot in the past for hacking things together. It translates well both to Ruby on Rails (front end) and to C (with low level server magic).

Re:When To Write Bad Code by brandonsavage on Tuesday January 29, 2013 @12:22PM (#5135103)
This is a great suggestion. I've done this with PHP (the first language I learned) for work I'm doing in Python. It also helps sometimes when you have to translate code from one language to another to use an intermediary language.
Re:When To Write Bad Code by LukeShu on Tuesday January 29, 2013 @11:52AM (#5134930)
That's an interesting tip. I'm going to try that.