You can never expect a kickass programmer to also have the best design chops. They require different forms of thinking. So stop giving false advise to programmers on enlisting design skills and instead partner with the best designers!
You can never expect a kickass programmer to also have the best design chops. They require different forms of thinking. So stop giving false advise to programmers on enlisting design skills and instead partner with the best designers!
If you're a programer and not a designer, just think of your design as another optimization point.
Whenever I worry about the design/branding of my current startup, I visit the historical timeline of amazon's logo as a reminder that we'll be able to make it better eventually, but there's more important things to work on now: http://www.kokogiak.com/gedankengang/2004/07/amazoncom-logo-...
On the other hand, communications design—what you call "pretty colors and interface"—is an entirely different set of skills, honed mainly by years of critical exposure to different visual aesthetics and artisanal practice in replicating those aesthetics to understand their composition. It's an orthogonal skill to programming—but, once it has been done and a suitable aesthetic created for a piece, it's pretty easy for a programmer to take the results (a "theme"), break it down structurally into re-usable components, and then apply those components to solve their problems. The bit the programmer is untrained at, the understanding of what works with what, has already been performed by the designer.
For $15, you probably won't get the most absolutely-custom-tailor-made experience - but you might at least get something that convinces visitors to take a closer look.