Earlier quoted context omitted.
> He is a terrible, terrible coder. I've had an idea brewing in my head for quite some time, and while I still don't quite have the words to express it completely, it more or less boils down to this: There isn't necessarily a correlation between being a good programmer and shipping a successful product. Now of course we can argue over the definition of "good programmer" and "successful product". I started as a hobby…
> Lately I've realized that having pristine, elegant code is NOT the goal. The goal is to ship software that people actually use. It depends on the use case and business model of your software. If you want to ship a single version of something then don't worry about code quality. If you're market testing and will get resources for a rewrite if the product takes off then again speed to market is more important than co…
There are vast discussions about this both online and in books, referring to "sloppy code" as "technical debt". Just like monetary debt, sometimes it is worth taking on a significant debt, while there are other times that it is best to avoid debt. It's a judgement call either way, and I've found that I tend to err on the side of being too scared of technical debt.