Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Developer Experience Matters

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers.

Developer Experience Matters

(I gave this talk at DevRel Summit on August 2016, in Seattle).

User-Experience (UX) focuses on understanding what users' needs and value, and provide practical products or services. This human-computer interaction acts the same when the users are developers. This talk focuses on Developer-Experience (DX), to establish a good relationship between developers and platform or API providers.

Avatar for Tomomi Imura

Tomomi Imura

October 11, 2016
Tweet

More Decks by Tomomi Imura

Other Decks in Technology

Transcript

  1. @girlie_mac Tomomi (@girlie_mac) does: • advocate open web & technology

    • front-end engineering • writer & speak about tech • mentor
  2. @girlie_mac More Bio... • Lead Dev Evangelist at PubNub ◦

    2014-16 - Realtime Data Stream SDKs • Sr. Dev Evangelist at Nokia ◦ 2014- Strategy for upcoming mobile platform ◦ 2012- HTML5 evangelist, worked with W3C • Sr. DevRel Engineer at Palm (then HP) ◦ 2011- webOS partners & app developers
  3. @girlie_mac Before DevRel... • Human Interface Developer at Palm ◦

    2009- webOS User interface & experience ...and this is why I approach DevRel differently!!!
  4. @girlie_mac User-Experience “User-Experience (UX) focuses on having a deep understanding

    of users, what they need, what they value, their abilities, and also their limitations.” Source: usability.gov
  5. @girlie_mac User-Experience “User-Experience (UX) focuses on having a deep understanding

    of users, what they need, what they value, their abilities, and also their limitations.” Source: usability.gov
  6. @girlie_mac Developer-Experience “Developer-Experience (DX) focuses on having a deep understanding

    of developers, what they need, what they value, their abilities, and also their limitations.”
  7. @girlie_mac Bad UX: User Reactions 1. Get confused 2. Guess

    and fail 3. Frustrated 4. Repeat 2 - 3 5. Totally pissed off
  8. @girlie_mac Bad DX: Developer Reactions 1. Get confused about enigmatic

    APIs 2. console.log(wtf) & error 3. Frustrated 4. Repeat 2 - 3 5. Totally pissed off
  9. @girlie_mac Developer-Centric Products • Platforms • SDKs & tools •

    APIs • Developer website UI/UX, and contents • Docs, tutorials, and “Get started” guides • Sample code - GitHub code & README
  10. @girlie_mac Bad DX Examples: APIs • Badly designed APIs ◦

    Bad naming conventions ◦ Bad error messages ◦ Inconsistent ◦ etc. • Poor documentation
  11. @girlie_mac Bad DX Examples: Docs & Tuts • No documentation

    • Bad browsing experience, no ref links • No diagram, screenshot, picture etc. • Too complex • Outdated materials • Too much marketing • PDF everything (Docs != Whitepaper)
  12. @girlie_mac DEVELOPERS, DEVELOPERS, DEVELOPERS! How can I end my talk

    about developer experiences w/o this perspirational photo of Ballmer!? LOL!