SINFO Keynote - Technical Principles of Developer Experience (DX)

Slide 1

Slide 1 text

Shodipo Ayomide | Keynote - SINFO, Lisbon, Portugal 2021 Technical Principles of Developer Experience (DX)

Slide 2

Slide 2 text

Shodipo Ayomide Dev. Relations Manager at Stack Overflow • GitHub Star • Cloudinary Media Developer Expert • Community Evangelist Twitter & GitHub @developerayo

Slide 3

Slide 3 text

What is Developer Experience (DX)?

Slide 4

Slide 4 text

Developer experience (DX) is similar to how you see and understand user experience (UX) but the difference is DX focus is strictly on developers who consume certain API services, SDKs, or other services owned by a company or an organisation.

Slide 5

Slide 5 text

We help developers feel awesome and great about their work, because the transition into docs to product use case was easy.

Slide 6

Slide 6 text

Popular Question: Who is a Developer Advocate? 1. Technically Advanced 2. A Community Builder 3. Expert Communicator of Technicalities 4. Can Sell Software to Developers

Slide 7

Slide 7 text

User Experience (UX) is how the general users use your platform and their experience from loading up the first screen to signing up so routing to their dashboard.

Slide 8

Slide 8 text

Developer Experience (DX) is the flow developers have while trying to implement or configure your dev SDK, API, or your NPM package.

Slide 9

Slide 9 text

The difference: Developer Focused | General User Experience Focus.

Slide 10

Slide 10 text

Developer Experience is Value & Time Value - I can reach my goals with this API - This API provides even more than I need right now, exciting! Time - I can reach my goals in a shorter time - This API docs is amazingly straightforward!

Slide 11

Slide 11 text

Productivity of developers is measured in DX based on how fast developers move from docs to implementation.

Slide 12

Slide 12 text

Documentation

Slide 13

Slide 13 text

No docs, it’s simply called, I built this I don't care figure it out yourself, I hate stress 😬

Slide 14

Slide 14 text

The most important part of writing good docs is the structure, everything should be tabled properly and super easy to find.

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

Everyone love a well structured ReadMe

Slide 18

Slide 18 text

What happen’s under the hood when there is no docs:

Slide 19

Slide 19 text

Developers need to understand how your API service works, what endpoints are available, how to implement them, All these are great developer experience because it helps developers move from your docs to getting their api key/tokens to implementation.

Slide 20

Slide 20 text

Tools for helping with docs: - Docusaurus (JS) - Documentationjs (JS) - Gocco (GO) - Slate (Ruby) - Codex2 (PHP)

Slide 21

Slide 21 text

Documentation is not just for the end-user, you need it also, you are human, you forget things.

Slide 22

Slide 22 text

Commit Messages

Slide 23

Slide 23 text

Commit messages are part of documenting your code also. Which helps in improving the flow of onboarding new developers to the dev team,

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

Developer Experience Feedback Can be hurtful but it helps to improve the product. Any feedback is good feedback ✅ ❌

Slide 26

Slide 26 text

ImageHive.co

Slide 27

Slide 27 text

Thank You! Questions? You can also follow and reach me over on: Twitter: @developerayo GitHub: @developerayo Shodipo Ayomide | Keynote - SINFO, Lisbon, Portugal 2021