korrents
Tom Preston-Werner

What Tom Preston-Werner thinks about design

@tom-preston-werner · 10 positions · On ppll ↗

Programmer and entrepreneur; co-founded GitHub and created Jekyll, Gravatar and the Semantic Versioning spec.

Tom Preston-Werner 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.

Filter design · Newest first
Topic
All 10design 3startups 3America 2JavaScript 2racism 2climate change 1software performance 1venture capital 1
Sort
NewestOldest

Only Tom Preston-Werner on design. See everyone on design

3 dated positions, 2022 to 2023, in their own words. Our reading of what Tom Preston-Werner has said — not written or endorsed by them.

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

  1. Our readingBuilding a secure, performant GraphQL API is tricky and adds real cost during early-stage app prototyping.

    Their wordsWhile we love GraphQL for many use cases, implementing a secure and performant GraphQL API can be tricky and there is a definite cost to requiring it during early prototyping of your app.

    ↗RedwoodJS’ Next Epoch: All In on React Server Componentstom.preston-werner.com 1st of 3 in this piece

  2. 12 months earlier

  3. Our readingMajor version numbers should not be treated as sacred, and any breaking change deserves a major bump regardless of size.

    Their wordsIf we want to live in a world where SemVer improves our collective experience as much as possible, it means we need to believe something new: Major version numbers are not sacred.

    ↗Major Version Numbers are Not Sacredtom.preston-werner.com 1st of 2 in this piece

  5. Our readingBreaking changes should be released frequently in small batches rather than saved up for one big yearly major version.

    Their wordsI actually prefer more frequent major versions with smaller sets of breaking changes. There is a real danger in saving up all your significant changes and releasing them in one whopping major version once a year.

    ↗Major Version Numbers are Not Sacredtom.preston-werner.com 2nd of 2 in this piece