Developer Experience, API design and craft skills

Slide 1

Slide 1 text

DEVELOPER EXPERIENCE, API DESIGN AND CRAFT SKILLS

Slide 2

Slide 2 text

www.oshineye.com/+

Slide 3

Slide 3 text

www.oshineye.com/+

Slide 4

Slide 4 text

ACQUISITION TRANSMISSION GROWTH SKILL

Slide 5

Slide 5 text

API DESIGNERS IN THE ROOM?

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

1 UX techniques for developer-facing products 2 Focus on the OOB experience 3 Use convention over conﬁguration 4 Design away common problems

Slide 9

Slide 9 text

UX TECHNIQUES FOR DEVELOPERS

Slide 10

Slide 10 text

FOCUS ON THE OUT-OF-BOX EXPERIENCE

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

CONVENTION OVER CONFIGURATION

Slide 13

Slide 13 text

DESIGN AWAY COMMON PROBLEMS

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

AFFORDANCES

Slide 18

Slide 18 text

ZUHANDEN READY-TO-HAND

Slide 19

Slide 19 text

VORHANDEN PRESENT-AT-HAND

Slide 20

Slide 20 text

API DESIGN & API USE

Slide 21

Slide 21 text

ASPIRATIONAL

Slide 22

Slide 22 text

EXAMPLES PATTERNS HEURISTICS

Slide 23

Slide 23 text

DEVELOPEREXPERIENCE.ORG @DEVEXPFTW +DEVELOPER EXPERIENCE #devexp

Slide 24

Slide 24 text

RICHARD SENNETT AND THE SKILL OF REPAIR http://www.ﬂickr.com/photos/arselectronica/4953202301

Slide 25

Slide 25 text

REPAIR “making and repairing form a single whole” “it is by ﬁxing things that we often get to understand how they work”

Slide 26

Slide 26 text

STATIC REPAIR “the simplest way to make a repair is to take something apart, ﬁnd and ﬁx what’s wrong, then restore the object to its former state”

Slide 27

Slide 27 text

DYNAMIC REPAIR “a dynamic repair will change the object’s current form or function once it is reassembled” “the dynamic repair may involve a jump of domains, as when a mathematical formula corrects a defect in observed data. Or the dynamic repair may invite new tools for working with objects”

Slide 28

Slide 28 text

CONTINUUM OF MAKING AND REPAIRING 1 New code 2 Refactoring 3 Legacy code

Slide 29

Slide 29 text

SKILL AND COMMUNITY “in craftwork, people can and do improve” “the isolated expert sends a signal that the organization is in trouble” “too many modern experts imagine themselves in the Stradivari trap−indeed, we could call the Stradivari Syndrome the conviction that one’s expertise is ineffable...as a result their skills degrade over time in comparison with doctors who turn outward professionally”

Slide 30

Slide 30 text

REFACTORING != REPAIR Refactoring: behaviour-preserving transformation Transformation in other dimensions Repair focusses on change in various dimensions

Slide 31

Slide 31 text

EXAMPLE: FEEDPARSER

Slide 32

Slide 32 text

BROKEN? Last release: 2007 XXX open bugs and patches Supported ancient versions of Python Standard Feedparser for Python (and other) communities

Slide 33

Slide 33 text

BROKEN? No new committers in years Centralised development Comprehensive acceptance suite

Slide 34

Slide 34 text

START SMALL, CONCRETE AND PUBLIC

Slide 35

Slide 35 text

START SMALL, CONCRETE AND PUBLIC

Slide 36

Slide 36 text

EMBRACE POSITIVE DEVIATION AND DYNAMIC REPAIR

Slide 37

Slide 37 text

REPAIR IS A SKILLED PROCESS OF RENEWAL NOT AN EVENT

Slide 38

Slide 38 text

AFFORDANCE AND SKILL

Slide 39

Slide 39 text

EMPATHY AND API DESIGN

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

INFORMATION IS WORTHLESS IF IT DOESN’T CHANGE YOU

Slide 45

Slide 45 text

CHANGE A LITTLE

Slide 46

Slide 46 text

THANK YOU!