Work should be broken into manageable chunks, and a designer should not send an engineer a 500-line PR they did not even review themselves.

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.

software quality Whether a program is any good and how anyone would know: tests, review, debt, and what a suite cannot cover.