forked from hakimel/reveal.js
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathlets_make_writing_API_documentation_interesting_for_developers.html
executable file
·1141 lines (1060 loc) · 40 KB
/
lets_make_writing_API_documentation_interesting_for_developers.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<title>Let's make writing API documentation interesting for developers</title>
<meta name="description" content="Let's make writing API documentation interesting for developers">
<meta name="author" content="Milan Popovic">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/black.css">
<link rel="stylesheet" href="css/presentation/lets_make_writing_API_documentation_interesting_for_developers.css">
<!-- Theme used for syntax highlighting of code -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement('link');
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match(/print-pdf/gi) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName('head')[0].appendChild(link);
</script>
</head>
<body>
<div class="reveal">
<div class="slides">
<section>
<h1>Let's make writing API documentation interesting for developers</h1>
<p>
<small>Presented by <a href="http://milanpopovic.me">Milan Popović</a> / <a
href="http://twitter.com/komita1981">@komita1981</a></small>
</p>
</section>
<section>
<h2>
3 biggest software lies
</h2>
<p class="left_align fragment">
The program is fully tested and bug-free
</p>
<p class="left_align fragment">
Of course we can modify it
</p>
<p class="left_align fragment red_text">
We are working on the documentation
</p>
</section>
<section>
<h2>
API
</h2>
<p class="left_align">
At the core of modern software development and architecture
</p>
<p class="left_align">
Massive market
</p>
<p class="left_align">
Tens of millions of microservices
</p>
<p class="left_align">
Millions of private APIs
</p>
<p class="left_align">
10000s of public APIs
</p>
<aside class="notes">
@source
https://www.slideshare.net/DialexaLLC/building-an-api-using-api-documentation-to-overcome-4-key-challenge
</aside>
</section>
<section>
<p class="left_align">
<q>
An API Is Only As Good As Its Documentation
</q>
</p>
<p class="right_align">
Unknown hero
</p>
<aside class="notes">
</aside>
</section>
<section>
<p class="left_align">
<q>
I'll write the documentation tomorrow...
</q>
</p>
<p class="right_align">
Unknown coward :-)
</p>
<aside class="notes">
@source https://speakerdeck.com/loonypandora/documentation-for-fun-and-profit
Speak with audience:
Hands up - who say this all the time
Who hates to write documentation?
Do you document your API?
Developers who love to write documentation are pretty rare
</aside>
</section>
<section>
<section>
<h2>
Documentation is...
</h2>
<p class="left_align">
About communication
</p>
<p class="left_align">
Important for all team members
</p>
<p class="left_align">
Complex
</p>
<p class="left_align">
Discipline
</p>
<aside class="notes">
@source https://speakerdeck.com/katherinemwhite/documentation-for-developers
@source https://speakerdeck.com/ericholscher/documentation-as-empathy
I can't say I'm self taught. I've been taught by the people who wrote the documentation
@soulshake
@source https://speakerdeck.com/lucas/documentation-for-fun-and-profit
@source https://speakerdeck.com/apistrat/a-developers-approach-to-documentation-by-gregory-koberger
@source https://speakerdeck.com/adekunleoduye/documentation-driven-design-systems
@source https://www.slideshare.net/wojtassj/pycon-pl-2014-executable-api
It's more than tool because it represents that you care about your consumers (and
your colleagues)
</aside>
</section>
<section>
<section>
<h2>
Documentation is...
</h2>
<p class="left_align">
A critical component to the usability of your API
</p>
<p class="left_align">
A critical component to API success
</p>
<p class="left_align">
UI for your API
</p>
<p class="left_align">
More than tool
</p>
<p class="left_align">
Last thing on the list :-)
</p>
</section>
</section>
<section>
<h2>
Documentation is not..
</h2>
<p class="left_align">
One man job
</p>
<p class="left_align">
About your API - it’s about your users
</p>
<p class="left_align">
Only used by humans - it can be consumed by machines
</p>
</section>
</section>
<section>
<section>
<h2>
Good Documentation Should Be:
</h2>
<p class="left_align">
Easy to understand
</p>
<p class="left_align">
Reliable
</p>
<p class="left_align">
Readable (readable === useful)
</p>
<p class="left_align">
Complete
</p>
<p class="left_align">
Concise
</p>
<p class="left_align">
Consistent
</p>
<aside class="notes">
@source https://speakerdeck.com/evildmp/documentation-driven-development
Structured properly = how-to, tutorials
@source https://speakerdeck.com/kneath/documentation-is-freaking-awesome
@source https://speakerdeck.com/loonypandora/documentation-for-fun-and-profit
@source https://www.slideshare.net/eBrandingNinja/apithedocs-how-can-api-documentation-be-agile
@source https://www.slideshare.net/mikestowe/api-documentation-best-practices
Just as important as reliability is readability.
Code should not be shipped if it is not documented
</aside>
</section>
<section>
<h2>
Good Documentation Should Be:
</h2>
<p class="left_align">
With valid and working examples
</p>
<p class="left_align">
Always up-to-date
</p>
<p class="left_align">
Structured properly
</p>
<p class="left_align">
Within the structure clear and consistent
</p>
<p class="left_align">
Be part of development process
</p>
</section>
<section>
<h2>
Good Documentation Should Be:
</h2>
<p class="left_align">
Searchable
</p>
<p class="left_align">
Version controlled
</p>
<p class="left_align">
Canonical
</p>
<p class="left_align">
Something you want to do
</p>
</section>
<section>
<p class="left_align">
1. Good documentation can’t fix a bad API. A lot of people fix bad APIs by just writing a lot of
documentation
</p>
<p class="left_align">
2. A good API can’t be used without good documentation
</p>
<p class="left_align">
Greg Koberger, ReadMe
</p>
<aside class="notes">
@source https://www.slideshare.net/eBrandingNinja/right-ingredients-for-your-api-documentation
</aside>
</section>
</section>
<section>
<section>
<h2>
Good Documentation Benefits:
</h2>
<p class="left_align">
Empower people to use your API in the most efficient and right way
</p>
<p class="left_align">
Makes product easier to understand
</p>
<p class="left_align">
More consumers
</p>
<p class="left_align">
Less support requests
</p>
<aside class="notes">
@source https://speakerdeck.com/danabrit/documentation-is-win-or-wtfm
Title in source is - Why is documentation win
@source https://speakerdeck.com/kneath/documentation-is-freaking-awesome
</aside>
</section>
<section>
<h2>
Good Documentation Benefits:
</h2>
<p class="left_align">
Owning great and important marketing tool
</p>
<p class="left_align">
You will become better writer
</p>
<p class="left_align">
Accelerate developer onboarding
</p>
</section>
</section>
<section>
<section>
<h2>
What should you document:
</h2>
<p class="left_align">
General description
</p>
<p class="left_align">
HTTP status codes
</p>
<p class="left_align">
HTTP verbs
</p>
<p class="left_align">
Headers
</p>
<p class="left_align">
Versioning
</p>
<aside class="notes">
@source https://speakerdeck.com/ankinson/documenting-restful-apis-2
@source https://speakerdeck.com/ichesnokov/developing-documentation-for-restful-apis
</aside>
</section>
<section>
<h2>
What should you document:
</h2>
<p class="left_align">
Resources - input/output
</p>
<p class="left_align">
Responses - OK & errors
</p>
<p class="left_align">
Authentication and authorisation
</p>
<p class="left_align">
Rate limiting
</p>
<p class="left_align">
Pricing
</p>
</section>
</section>
<section>
<section>
<h2>
API Success
</h2>
</section>
<section>
<p class="left_align">
<q>
The way to a developer’s heart is great documentation.
</q>
</p>
<p class="right_align">
James Ju, Parse
</p>
<aside class="notes">
@source https://www.slideshare.net/eBrandingNinja/right-ingredients-for-your-api-documentation
</aside>
</section>
<section>
<p class="left_align">
With the popularity of microservices, developers are your decision makers
</p>
<p class="left_align">
They will judge your API in a manner of seconds
</p>
<p class="left_align">
Developer experience is the most important part of the API economy
</p>
<p class="left_align">
The quality of your API's documentation dictates the developer experience
</p>
<p class="left_align">
Designing an engaging experience around your API
</p>
<aside class="notes">
@source https://www.slideshare.net/eBrandingNinja/right-ingredients-for-your-api-documentation
Most important factor for usage of third party is complete and accurate documentation
@source
https://www.slideshare.net/DialexaLLC/building-an-api-using-api-documentation-to-overcome-4-key-challenges
The quality of your API's documentation dictates the developer experience.
@source https://www.slideshare.net/mikestowe/api-documentation-best-practices
</aside>
</section>
<section>
<h2>
Litmus test - 3:30:3 goal
</h2>
<p class="left_align">
You have 3 minutes, 33 seconds to sell your API
</p>
<p class="left_align">
Understand in 3 seconds what your API is for
</p>
<p class="left_align">
Be able to identify the entry point in 30 seconds
</p>
<p class="left_align">
Be able to create an account, call the system, and use the result in 3 minutes
</p>
<p class="left_align">
Ori Pekelman, Platform.sh
</p>
<aside class="notes">
@source https://www.slideshare.net/eBrandingNinja/right-ingredients-for-your-api-documentation
</aside>
</section>
<section>
<p class="left_align">
3 seconds - what it does
</p>
<p class="left_align">
30 seconds - why you should use it
</p>
<p class="left_align">
3 minutes - to do something
</p>
<aside class="notes">
@source https://www.slideshare.net/ellispratt/moving-into-api-documentation-writing
</aside>
</section>
</section>
<section>
<section>
<h2>
How to write good documentation:
</h2>
<p class="left_align">
Treat documentation as you treat your code
</p>
<p class="left_align">
Integrate in review process
</p>
<p class="left_align">
Improve it constantly (do refactoring)
</p>
<p class="left_align">
Integrate in development cycle
</p>
<p class="left_align">
Allow tracking of documentation issues
</p>
<aside class="notes">
@source https://speakerdeck.com/indigo/we-dont-need-no-documentation
@source https://speakerdeck.com/ankinson/documenting-restful-apis-2
TDD - test driven documentation
@todo Find some picture with tdd
More code we have - we need to invest more time for maintenance. The same is with
documentation.
</aside>
</section>
<section>
<h2>
How to write good documentation:
</h2>
<p class="left_align">
Add it to your acceptance criteria (done === documented)
</p>
<p class="left_align">
Provide some guarantees that the documentation is accurate - let's TDD
</p>
<p class="left_align">
Write like a human for humans
</p>
<p class="left_align">
Write like a machine for machines
</p>
</section>
</section>
<section>
<section>
<h2>
Documentation problems
</h2>
<p class="left_align">
Does not exists
</p>
<p class="left_align">
Write documentations just to have it
</p>
<p class="left_align">
Outdated
</p>
<p class="left_align">
Costly to maintain
</p>
<p class="left_align">
Boring
</p>
<p class="left_align">
Time consuming
</p>
<aside class="notes">
@source https://speakerdeck.com/danabrit/documentation-is-win-or-wtfm
Title in source is - The case against Documentation
@source https://speakerdeck.com/indigo/we-dont-need-no-documentation
@source https://speakerdeck.com/lucas/documentation-for-fun-and-profit
Can get outdated easily - Isn't easy to fix
@source https://www.slideshare.net/eBrandingNinja/apithedocs-how-can-api-documentation-be-agile
Complicated documentation is sign that your code is too complicated
Out of sync documentation isn’t only not useful, but detrimental to the usability of your API.
</aside>
</section>
<section>
<h2>
Documentation problems
</h2>
<p class="left_align">
Can get outdated easily
</p>
<p class="left_align">
Too complicated
</p>
<p class="left_align">
Lack of ownership
</p>
<p class="left_align">
People don't use API that do not have good documentation
</p>
<p class="left_align">
It's just wrong
</p>
</section>
</section>
<section>
<section>
<h2>
What API consumer wants:
</h2>
<p class="left_align">
To try your API before they write code
</p>
<p class="left_align">
To explore data/functionality you provide
</p>
<p class="left_align">
Accurate, clear, concise and up-to-date information
</p>
<p class="left_align">
To quickly implement API
</p>
<p class="left_align">
To understand what is happening
</p>
<aside class="notes">
@source https://www.slideshare.net/biztalk360/api-documentation-77860485
@source https://www.slideshare.net/MartaRauch/rest-api-documentation-best-practices
</aside>
</section>
<section>
<h2>
What API consumer wants:
</h2>
<p class="left_align">
Modern, usable UX
</p>
<p class="left_align">
Sendbox test environment
</p>
<p class="left_align">
Help (blogs, twitter, recent update info...)
</p>
<p class="left_align">
Client in the language of choice
</p>
</section>
</section>
<section>
<h2>
Examples of Great API Documentation
</h2>
<p class="left_align">
Stripe
</p>
<p class="left_align">
Twilio
</p>
<p class="left_align">
Shopify
</p>
<p class="left_align">
Spotify
</p>
<p class="left_align">
Sendgrid
</p>
</section>
<section>
<section>
<h2>
A few more things...
</h2>
<p class="left_align">
How to start? Just start writing...
</p>
<p class="left_align">
Decide on set of conventions (naming, markup, capitalization, styles)
</p>
<p class="left_align">
Stick to conventions
</p>
<p class="left_align">
Assume no prior knowledge for users
</p>
<aside class="notes">
@source https://speakerdeck.com/danabrit/documentation-is-win-or-wtfm
Assume no prior knowledge for users - terms that are obvious to you might not be
obvious to others
@source https://speakerdeck.com/limedaring/nodeconf-budapest
</aside>
</section>
<section>
<h2>
A few more things...
</h2>
<p class="left_align">
Provide examples (in several languages)
</p>
<p class="left_align">
Use gender-neutral language
</p>
<p class="left_align">
Cut down your content (2-3 sentences per paragraph)
</p>
<p class="left_align">
Make it easy to skim
</p>
</section>
</section>
<section>
<section>
<h2>
A documentation-first approach
</h2>
<p class="left_align">
It's like TDD for API
</p>
<p class="left_align">
Detailed explanation of what the API is meant to do
</p>
<p class="left_align">
Contract between your API and it's consumers
</p>
<p class="left_align">
Eliminate all challenges and improve the developer experience
</p>
<p class="left_align">
By standardizing the communications between all parties you can actually start to build the API
</p>
<aside class="notes">
@source
https://www.slideshare.net/DialexaLLC/building-an-api-using-api-documentation-to-overcome-4-key-challenges
@source https://speakerdeck.com/galenandrew/building-better-apis-documentation
standardizing the communications === creating detailed contract
</aside>
</section>
<section>
<h2>
A documentation-first approach
</h2>
<p class="left_align">
Slow down - plan your API
</p>
<p class="left_align">
Write good documentation
</p>
<p class="left_align">
Test code against documentation
</p>
<p class="left_align">
Provide mocks for consumers (fellow developers)
</p>
</section>
<section>
<h2>
3 type of tools to the rescue
</h2>
<ul>
<li>Modelling tools</li>
<li>Testing tools</li>
<li>Presentation tools</li>
</ul>
</section>
</section>
<section>
<section>
<h2>
Modelling tools
</h2>
<p class="left_align">
API Blueprint
</p>
<p class="left_align">
Swagger
</p>
<p class="left_align">
RAML
</p>
<p class="left_align">
I/O Docs
</p>
<p class="left_align">
Apigee
</p>
</section>
<section>
<h2>
Api blueprint
</h2>
<p class="left_align">
From apiary.io - but can be used independently
</p>
<p class="left_align">
A powerful high-level API description language for web APIs
</p>
<p class="left_align">
Focused on collaboration
</p>
<p class="left_align">
Allow us to prototype - write spec
</p>
<p class="left_align">
Recognized by GitHub as language - .apib as extension
</p>
<aside class="notes">
@source https://www.slideshare.net/eBrandingNinja/apithedocs-how-can-api-documentation-be-agile
</aside>
</section>
<section>
<h2>
MSON - Markdown Syntax for Object Notation
</h2>
<p class="left_align">
Plain-text, human and machine readable, description format for describing data structures in common
markup formats such as JSON, XML or YAML.
</p>
<p class="left_align">
Facilitate the discussion & validation of data structures
</p>
<p class="left_align">
Developed by Apiary as a part of the API Blueprint syntax
</p>
<p class="left_align">
Typical API Docs = Route + Json
Api Blueprint = Markdown + MSON
</p>
</section>
<section>
<h2>
Tools
</h2>
<p class="left_align">
Apiary
</p>
<p class="left_align">
Drafter
</p>
<p class="left_align">
Drakov
</p>
<p class="left_align">
Aglio
</p>
<p class="left_align">
Blueman
</p>
<p class="left_align">
Api-Mock
</p>
<p class="left_align">
Many more useful tools - please check documentation
</p>
</section>
<section>
<h2>
Tips
</h2>
<p class="left_align">
Use Data Structures
</p>
<p class="left_align">
Do not generate it from annotations
</p>
<p class="left_align">
Use boilerplate - https://github.com/jsynowiec/api-blueprint-boilerplate
</p>
</section>
</section>
<section>
<section>
<h2>
Dredd
</h2>
<p class="left_align">
Language-agnostic command-line tool for validating API description document against backend
implementation of the API.
</p>
<p class="left_align">
Interacts with the backend app only through the HTTP layer.
</p>
<p class="left_align">
Ensure accurate documentation (documentation matches implementation)
</p>
<p class="left_align">
Tests fail when documentation is missing or out-of-date
</p>
<aside class="notes">
@source https://speakerdeck.com/jlstrater/test-driven-approaches-to-documenting-restful-apis-1
</aside>
</section>
<section>
<h2>
Cycle
</h2>
<p class="left_align">
Perform request
</p>
<p class="left_align">
Assert status code
</p>
<p class="left_align">
Assert headers
</p>
<p class="left_align">
Assert body payload
</p>
<aside class="notes">
@source https://speakerdeck.com/honzajavorek/2016-1
</aside>
</section>
<section>
<h2>
Supported formats
</h2>
<p class="left_align">
API Blueprint
</p>
<p class="left_align">
Swagger
</p>
<aside class="notes">
</aside>
</section>
<section>
<h2>
Hooks
</h2>
<p class="left_align">
Before & after all
</p>
<p class="left_align">
Before & after each
</p>
<p class="left_align">
Before & after (Users > Users Collections > List Users)
</p>
<p class="left_align">
Before each validation
</p>
<p class="left_align">
Before validation (Users > Users Collections > List Users)
</p>
</section>
<section>
<h2>
Hooks - supported languages
</h2>
<p class="left_align">
PHP
</p>
<p class="left_align">
Go
</p>
<p class="left_align">
Node.js
</p>
<p class="left_align">
Python
</p>
<p class="left_align">
Ruby
</p>
<p class="left_align">
Rust
</p>
<p class="left_align">
Perl
</p>
</section>
</section>
<section>
<section>
<h2>
Display tools
</h2>
<p class="left_align">
Lets make it beautiful
</p>
<p class="left_align">
We are engineers not designers :-)
</p>
<aside class="notes">
@source https://speakerdeck.com/loonypandora/documentation-for-fun-and-profit
</aside>
</section>
<section>
<p class="left_align">
Apiary
</p>
<p class="left_align">
Aglio
</p>
<p class="left_align">
PHPdraft
</p>
<p class="left_align">
Laravel blueprint docs
</p>
<aside class="notes">
</aside>
</section>
</section>
<section>
<section>
<h2>
A few more words about documentation
</h2>
<p class="left_align">
Forces us to slow down
</p>
<p class="left_align">
Puts us into different mindset
</p>
<p class="left_align">
Forces us to question our design
</p>
<p class="left_align">
Makes us think before we design
</p>
<p class="left_align">
Forces us to be in our API consumers shoes
</p>
<aside class="notes">
@source https://speakerdeck.com/kneath/documentation-is-freaking-awesome
@source https://speakerdeck.com/loonypandora/documentation-for-fun-and-profit
</aside>
</section>
<section>
<h2>
A few more words about documentation
</h2>
<p class="left_align">
It's still hard but at least it's a little less painful now
</p>
<p class="left_align">
Lots of energy and opportunity in this field
</p>