korrents
Andy Madrick

What Andy Madrick thinks about vibe coding

@andy-madrick · 20 positions · 0 changes of mind

Product designer who led the design of Notion's meeting notes as of May 2026, previously at Tome and Mercury.

Everything they publish, on ppll ↗

Andy Madrick did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

3 dated positions, 2026, in their own words. Our reading of what Andy Madrick has said — not written or endorsed by them.

3 positions so far — this page is not yet offered to search engines.

  1. Our readingCoding tools are very good at executing motion design, but you have to be very descriptive about what you want, otherwise you will be fighting them for hours.

    design

    Their wordsI think with a lot of this motion design stuff, coding tools are so good at executing it, but you have to be very, very descriptive about what you want, otherwise you're going to be fighting these things for like hours.

    ↗Andy Madrick - Why AI changed design handoff foreveryoutube.com 1st of 20 in this recording

  3. Our readingAsking an agent to keep an engineer's functionality and apply a designer's styling can get much closer than intuition says it would.

    design

    Their wordsCan you keep all the functionality of the engineer's version and give it all the styling that I have here. And I think that can get you so much closer than I think like our intuition says it would.

    ↗Andy Madrick - Why AI changed design handoff foreveryoutube.com 8th of 20 in this recording

  5. Our readingWork 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

    Their wordsWe have to break the work into like manageable chunks. Like five lines is not very realistic, but a hundred-line PR, that's my general advice of like don't five-code a bunch of stuff and send an engineer a 500-line PR that you didn't even review yourself.

    ↗Andy Madrick - Why AI changed design handoff foreveryoutube.com 11th of 20 in this recording