[raviisoccupied]

I am not an engineer, I can't look at code and determine if it is good, performant, or elegant. However, I can look at designs and make a judgement. I'm curious to see how Claude Design changes how I think about AI and its capabilities.

[hkpack]

If you are not a software engineer you can judge code the same way as you can judge design while not being a designer.

It is that in one case it is obvious for you that you don’t understand what you are looking at, and in another, for some reason, it is not.

[nerptastic]

I have a degree in design - it's one of those frustrating fields where laypeople really do believe they are experts. Mostly because... they can "see" it. It's easy to propose a change to a design. "Just move it to the right. Or left. Or make it green".

The end product is SUPPOSED to be simple to digest and understand, but the process behind that artifact is enigmatic. It may have taken months to determine the proper layout structure for a government website, but a certain end user can still say "Well... I would rather have the navbar on the right side."

Some of it is probably vocabulary as well. Software has jargon - design has jargon, but laypeople know how to say "bigger, smaller, right, left, red, blue". Frustrating, and part of why I left the field.

[raviisoccupied]

>If you are not a software engineer you can judge code the same way as you can judge design while not being a designer.

Very true.