Aller au contenu

Keep a friction log and read a sales book - product ownership with Joyce Er

23 septembre 2026 · 37 min

Notes de l’épisode

If execution got cheap and you still wait for someone to tell you what to build, this episode is for you. Kent talks with Joyce Er about five years owning features on VS Code, the jump to product at Cerebras, and why trust is the metric that tells you the work is working.

They cover daily stand-ups that roast your feature in public, friction logs as taste practice, dogfooding when you cannot be the user, qualifying customers instead of taking every check, and why a sales book belongs on a product engineer's shelf.

  • (00:00) - Meet Joyce Er
  • (01:18) - A dinner-plate AI chip
  • (02:47) - Engineering as we knew it shrunk
  • (04:38) - Ownership on the VS Code team
  • (07:33) - Why ownership matters more with AI
  • (10:23) - Keep a friction log
  • (12:18) - Judgment from lived experience
  • (15:33) - Invalidate old priors
  • (17:41) - VS Code's daily stand-up roast
  • (20:35) - When you cannot dogfood
  • (22:52) - Getting partner teams to help
  • (29:30) - Curiosity and time-boxing AI
  • (32:20) - Selling inference to coding tools
  • (34:00) - Qualify the right customer
  • (38:47) - Trust as the success metric
  • (40:11) - Homework: friction log and a sales book

Joyce Er spent five years as a software engineer on VS Code at Microsoft, with a front-row seat to GitHub Copilot and the shift from typing code to owning the why. About a year before this conversation she moved into product at Cerebras, the company behind dinner-plate wafer-scale chips for ultra-fast AI inference. The views in this episode are her own.

A major theme is ownership. On VS Code, every engineer owned the end-to-end definition of what shipped, not just the implementation. That only works with trust, dogfooding, and rituals that force you to defend the experience. Joyce describes a daily stand-up where you get five minutes to walk the feature, then the team roasts padding, consistency, and whether it belongs in the product. The lighter version is a bug bash. If people inside the company will not use the feature, that is a signal.

They also talk about how you grow judgment when nobody assigns the work. Joyce's first practice is a friction log: five minutes at the end of the day listing paper cuts in any software you used. Her more controversial homework is to read a sales book - she recommends The Qualified Sales Leader - so you understand how business value actually closes, especially when the product is not a credit-card checkout. Trust, she says, is the end-to-end metric: if customers and teammates trust you, you are doing the job.

Homework: keep a daily friction log, and read a book about sales.

Homework

  • Spend five minutes at the end of each day writing a friction log of paper cuts in software you used.
  • Read a sales book - Joyce recommends The Qualified Sales Leader - and notice how value gets sold at your company.
  • Use those notes the next time you decide what is worth building.

Resources

Guest: Joyce Er

Host: Kent C. Dodds

See on Epic Product Engineer

The views expressed by Joyce Er are her own and do not necessarily represent those of her employer.

Tous les épisodes de Become an Epic Product Engineer

Paramètres

Affichage

Langue

Détermine les stations affichées en premier sur la page d’accueil.

Historique

Les stations et épisodes écoutés récemment et tes dernières recherches sont seulement enregistrés dans ce navigateur.

Notifications

Un court message quand un podcast que tu suis publie un nouvel épisode. Désactive un podcast précis avec la cloche sur sa page.

Compte

Enregistrez vos favoris – dans l’app et sur le site.

Raccourcis clavier

/
Ouvrir la recherche
Espace
Lecture ou pause
← →
Dans le lecteur : 15 s en arrière, 30 s en avant (épisodes) · dans une rangée : tuile suivante
↑ ↓
Dans une rangée : cible dans la tuile
Début / Fin
Dans une rangée : première ou dernière tuile
Esc
Fermer la fenêtre ou le menu
?
Cet aperçu
En cours de lecture

Voir la station

À suivre

    Ajoutez des épisodes avec « À suivre » – ils seront lus après l'épisode en cours.