korrents
Guillermo Rauch

What Guillermo Rauch thinks about design

@guillermo-rauch · 52 positions · On ppll ↗

CEO of Vercel; creator of Next.js and Socket.IO. Writes at rauchg.com.

Guillermo Rauch 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.

11 dated positions, 2014 to 2026, in their own words. Our reading of what Guillermo Rauch has said — not written or endorsed by them.

  1. What's "best for humans" is no longer necessarily "best for business".

    ↗@rauchg on Xx.com

  2. 11 days earlier
  3. Btw, breaking apart the agent into these independent parts not only optimizes costs in a big way, it also *massively* improves security and auditability. I'd argue you can't even run a secure agent otherwise!

    ↗@rauchg on Xx.com

  4. 2 weeks earlier
  5. Skills are now a valuable form of software, like Emil's world-class design eng work. Projects like 𝚙𝚐𝚋𝚘𝚝, 𝚔𝚗𝚒𝚙, 𝚞𝚗𝚕𝚒𝚐𝚑𝚝𝚑𝚘𝚞𝚜𝚎 create amazing AI engineering loops.

    ↗@rauchg on Xx.com

  6. 11 days earlier
  7. The 'in between' is likely to be subsumed by agents producing just-in-time UI. When you need utilitarian content or data, it'll be generated just-in-time for you. Think of the agent as the new browser in this model.

    ↗@rauchg on Xx.com

  8. 11 years earlier
  9. And if I’m allowed to extrapolate, a clear path is now laid out towards a future where the steps to go from sketch to design to implementation are greatly more accessible to everyone with an idea.

    ↗Pure UIrauchg.com

  10. The fundamental idea I want to discuss is the definition of an application’s UI as a pure function of application state.

    ↗Pure UIrauchg.com

  11. The main issue, however, is that underestimating the size of the state space is actually very easy. In other words, it’s difficult to come up with the complete list of questions that your UI needs to answer.

    ↗Pure UIrauchg.com

  12. Lorem Ipsum has had a good run. Let’s replace it with data.

    ↗Pure UIrauchg.com

  13. 8 months earlier
  14. The bandwidth capacity of your users' connections might improve noticeably, as it steadily has, but the latency needle won't move much at all. This means that minimizing the number of roundtrips you make to display information on page is essential to great user experience and responsiveness.

    ↗7 principles of rich web applicationsrauchg.com

  15. A flexible enough system that can share rendering code between browser and server and provides tools for progressively loading scripts and styles will probably eliminate the colloquial distinction between websites and webapps. Both are reigned by the same UX principles. A blog and a CRM are fundamentally not that different.

    ↗7 principles of rich web applicationsrauchg.com

  16. JavaScript

    JavaScript allows us to mask network latency altogether. Applying this as a design principle should even remove most spinners or “loading” messages from your applications.

    ↗7 principles of rich web applicationsrauchg.com