[mcteapot]

Like programming good design takes practice. Just because you read a book is not going to make you a great designer. The question is are you willing to stop developing and put aside the time to design well or pay someone to do it for you.

[studiofellow]

False dichotomy. People are capable of doing more than one thing. I'm a designer who writes code. Developers can learn design basics, and doing so will serve them well!

You're right though about practice. That topic is on my outline.

[nsfmc]

well, i think the point is more "any time you're designing (or learning to design) is time you're not coding" (which, let's be honest, the times that you can actually be doing both at the same time are few and far between) for some folks that's not an acceptable tradeoff, for others it is.

[keeptrying]

You rarely have to do both at the same time.

IMHO if you've just started out on a startup - its better to be a designer because you can do customer devleopment without touching a line of code but by having a design which shows the customer exactly what to expect.

After you get a bunch of people begging you to build, then you build.

[studiofellow]

That's fair. I think it's about prioritizing. At some point, coding new features becomes less important than improving aspects of the design. So the tradeoff will vary with each situation.

[hopeless]

You're obviously right. But I don't want to be a great designer. As I said, I've got by with modifying ThemeForest templates but that's always someone else's design. I'd like to work on my own design fron scratch but, at a minimum, I'd like to have more design knowledge when selecting and modifying those templates.