Slide 1

Slide 1 text

DX is not the same as UX By Anil Kumar, Lokalise @anilbms75

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

@anilbms75

Slide 4

Slide 4 text

@anilbms75

Slide 5

Slide 5 text

Could you think how your experience at this conference has been thus far?

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

Experience

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

Applying User Experience Technique To Developer Experience

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

User Interview

Slide 12

Slide 12 text

Pair Programming

Slide 13

Slide 13 text

@anilbms75

Slide 14

Slide 14 text

@anilbms75

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

Pair Programming

Slide 17

Slide 17 text

@anilbms75

Slide 18

Slide 18 text

@anilbms75 DEVELOPER EXPERIENCE (DX) is not same as USER EXPERIENCE (UX) DX is for Makers UX is for consumers

Slide 19

Slide 19 text

Developer Persona Is Diverse

Slide 20

Slide 20 text

@anilbms75 Image: APIMatic

Slide 21

Slide 21 text

@anilbms75

Slide 22

Slide 22 text

@anilbms75 Image: React docs

Slide 23

Slide 23 text

What percentage of developers learn how to code using HOW TO VIDEOS? A. around 25% B. around 59% C. around 10% D. around 95% ✅

Slide 24

Slide 24 text

Overlooking Developer Needs

Slide 25

Slide 25 text

@anilbms75 “People don’t want a quarter-inch drill. They want a quarter-inch hole.” - Theodore Levitt

Slide 26

Slide 26 text

Train ticket Image source: wikipedia

Slide 27

Slide 27 text

Netflix Image source: undraw

Slide 28

Slide 28 text

Copilot Image source: unsplash

Slide 29

Slide 29 text

@anilbms75

Slide 30

Slide 30 text

Readme Image source: readme

Slide 31

Slide 31 text

@anilbms75

Slide 32

Slide 32 text

@anilbms75

Slide 33

Slide 33 text

@anilbms75

Slide 34

Slide 34 text

@anilbms75

Slide 35

Slide 35 text

@anilbms75

Slide 36

Slide 36 text

Lost in Troubleshooting

Slide 37

Slide 37 text

@anilbms75 Source: swyx.io

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

Jenni Nadler, Head of UX writing @ Wix

Slide 41

Slide 41 text

Image: @anilbms75 Developer Efficiency

Slide 42

Slide 42 text

@anilbms75 Feedback loop Source: martinfowler.com/articles/developer-effectiveness.html

Slide 43

Slide 43 text

@anilbms75 Developer Effectiveness Source: martinfowler.com/articles/developer-effectiveness.html

Slide 44

Slide 44 text

@anilbms75 How Can We Improve Developer Experience? Source: martinfowler.com/articles/developer-effectiveness.html

Slide 45

Slide 45 text

@anilbms75 Source: Unsplash 1. Time for value

Slide 46

Slide 46 text

@anilbms75 Time for value Source: Forma36

Slide 47

Slide 47 text

@anilbms75 Source: Chakra UI

Slide 48

Slide 48 text

2. Delight Quickly

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

@anilbms75

Slide 53

Slide 53 text

@anilbms75

Slide 54

Slide 54 text

@anilbms75

Slide 55

Slide 55 text

3. Feedback

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

Next Js Documentation Feedback Source: nextjs.org/docs

Slide 58

Slide 58 text

Lokalise Developer Hub Feedback From

Slide 59

Slide 59 text

4. User testing

Slide 60

Slide 60 text

Image: unsplash @anilbms75 “Dev tools user testing can be quick”

Slide 61

Slide 61 text

Dogfooding

Slide 62

Slide 62 text

@anilbms75 Image: Undraw Quick ways to find the participants? 1. Internal Engineers (solution engineers, professional service team, Developer advocates) 2. User testing with Pair programming 3. Friction Log Technique

Slide 63

Slide 63 text

@anilbms75

Slide 64

Slide 64 text

Image: unsplash @anilbms75 “If you want to know what a person really values, what they really suffer, what they really do, don’t listen to their words, observe their actions” - Amy Hoy, Sales Safari

Slide 65

Slide 65 text

Image: unsplash @anilbms75 Sharing observations

Slide 66

Slide 66 text

@anilbms75 Source: jpattonassociates.com

Slide 67

Slide 67 text

@anilbms75 Source: jpattonassociates.com

Slide 68

Slide 68 text

@anilbms75 Source: jpattonassociates.com

Slide 69

Slide 69 text

@anilbms75

Slide 70

Slide 70 text

@anilbms75 Image: Undraw 5. Friction Log Technique

Slide 71

Slide 71 text

@anilbms75 Image: Undraw How Can We Improve Developer Experience? 1. Delight quickly 2. Optimize for Developer Effectiveness 3. Dogfooding 4. User testing with Pair programming 5. Friction Log Technique

Slide 72

Slide 72 text

Thanks Twitter: @anilbms75 Email: [email protected] Linkedin: linkedin.com/in/anilkrishnashetty