Different kind of patterns. Design is about visual abstractions; code is more about textual and conceptual abstractions. The design space of a visual medium tends to be much easier to explore... visually.

(Also consider that a typical way of developing a website or application UI involves everything from drawing on paper through painting in Photoshop through building mockups in a graphics-oriented design package.)

I think at times we get too caught up in the visual components. Visuals like sketches and mockups and even code-less prototypes are perhaps best for communicating concepts, which is a part of design. But there's also the part of design that's less about communicating designs and more about applying the concept and designing a way that it can be created and engineered. That's where designing with code is extremely helpful.

So yeah, if I'm exploring or communicating ideas to non-technical people then yeah maybe code is less appropriate, but to say that you shouldn't design with code is ignoring a huge part of the design process.

Is architecture best represented in code? It's all about patterns.

Why do we have CAD tools at all when architects and engineers could just be writing code for buildings?

Some people need those visual metaphors in order to create something. There are people who think differently (from you) and a CAD tool would simply be a hindrance. And if the resulting building is top quality why care how the blueprints were made?

>Whats code? Patterns.

Im not trying to insult your work, but this is so grossly generalized and false that it's absurd.

You're not insulting my work at all :) On the contrary the fact that you're discussing it means you think it worthy of discussion.

But please note that programming mostly definitely is made up of patterns - ask any programmer. It's not absurd, nor a generalisation, it's a fact. If you're interested check these links out: http://code.tutsplus.com/articles/a-beginners-guide-to-desig... https://en.wikipedia.org/wiki/Software_design_pattern