Mocks and docs are dying: AI-native teams prototype and prune with code-first prototypes instead of static mocks and product requirement documents.

Drawn from what Julie Zhuo said

What these subjects mean

design How things should be made and judged: what makes a design good, who should do the designing, and what an interface is for.

vibe coding Building software by describing what you want and accepting what comes back, without reading much of it.

On the topicWhich mental models should a designer think with?under our view: Make it real: a prototype settles what a description cannot On the topicWho should design software, and how?under our view: The maker should work in the medium and shape it rough: build the thing, not a picture of it

What Julie Zhuo actually said

Do you hold this korrent?Do you also believe this?

In tension with

Any specific mockup from someone senior biases everyone after them, so early design should be breadboards and fat-marker sketches that leave room for designers.

Singer wants early design left rough — breadboards and fat-marker sketches — because a specific mockup from someone senior biases everyone downstream. Zhuo says mocks and docs are dying and that AI-native teams prototype in code instead. A working prototype is the most specific artefact of all, and it now arrives earlier than the mockup did.

Shared subject first, then similar wording. They may agree or disagree.