The Failure story through writing the first technical book

Transcript

1. The Failure story through writing the first technical book kkeeth

   @kuwahara_jsri @clown0082 Dec 21, 2020 #ٕज़ॻք۾Λ੝Γ্͛Δձ

2. Jun 19, 2020

3. Published a Riot.js book

4. Published a Riot.js book Please buy it https://www.amazon.co.jp/gp/product/4863543115

5. None

6. ...and my happy was for a moment

7. https://github.com/kkeeth/riot4-book-support/issues?q=is%3Aissue+is%3Aclosed

8. incoming many misspellings and typographical issues…

9. OMG !!

10. What was the problem? What was I supposed to do?

11. So, today I’d like to share some tips for writing

    technical books

12. Who am I ?

13. const my_info = { Workplace: ‘Yumemi Inc’, Position1: ‘Servant Leader

    of FET’, Position2: ‘Director’, Community: ‘Riot.js, Ionic, DIST’, PokemonGO: ‘TL40’ } About me

14. npm/~kkeeth

15. Sorry … This slide is made in English. But I

    am unfamiliar using English. So, I may have a wrong expression. Plz feedback for me called “Masakari” about my English!!

16. Analyze why this happened

17. ɾAbout writing env ɾWhat’s the stats ? Premise

18. My writing environment

19. https://docs.gitbook.com/ main tool used

20. usage about gitbook-cli

21. usage about gitbook-cli build for static HTML files

22. my book sample

23. One problem comes up when I'm writing

24. I want to count the number of characters…

25. I want to count the number of characters… Because books

    are usually about 1,400 characters per page. It takes about 200,000 characters to write a whole technical book.

26. You just have to make it, someone said

27. https://www.npmjs.com/package/wcmd created tool

28. created tool single file multiple files

29. My writing stats

30. ɾmy book has 334 pages ɾ230734 characters ɾabout 2 months

    ɾmy book is sole author my writing stats

31. more details https://note.com/clown0082/n/n7549641e5a9e

32. ɾBug in product ɾNot enough time for review ɾTypographical errors

    ɹand misprints Problems

33. Cause of the problems

34. writing and development at the same time Began in earnest

    2 months before the deadline Brushing up or change the product while writing MY BAD CASES I've stretched the schedule for drafts twice

35. Points: Make a firm plan and proceed steadily

36. Review & Fix Writing planning writing project Product Story

37. Review & Fix Writing planning writing project Product Story Books

    usually have a story (my book is too)

38. ɾCHAPTER 01 Riot.jsʹ͍ͭͯ஌Ζ͏ ɾCHAPTER 02 Riot.jsͷجૅ ɾCHAPTER 03 ͸͡ΊͯͷRiot.jsͰͷΞϓϦέʔγϣϯ։ൃ ɾCHAPTER

    04 Giphy APIΛར༻ͨ͠ΞϓϦέʔγϣϯ ɾCHAPTER 05 Riot.jsͰͷελΠϦϯά ɾCHAPTER 06 CMSͷ։ൃ my book index

39. ɾCHAPTER 01 Riot.jsʹ͍ͭͯ஌Ζ͏ ɾCHAPTER 02 Riot.jsͷجૅ ɾCHAPTER 03 ͸͡ΊͯͷRiot.jsͰͷΞϓϦέʔγϣϯ։ൃ ɾCHAPTER

    04 Giphy APIΛར༻ͨ͠ΞϓϦέʔγϣϯ ɾCHAPTER 05 Riot.jsͰͷελΠϦϯά ɾCHAPTER 06 CMSͷ։ൃ my book index intro Practice Basis

40. Review & Fix Writing planning writing project Product Story At

    first, we must get a review ❗ Next, get a review as well ❗

41. Review & Fix Writing planning writing project Product Story There

    are several perspectives, especially here ✋

42. ɾTypos and errors ɾCapitalize the beginning of nouns ɾConcrete rather

    than abstract ɾAmbiguous expression ɾFormatting e.g. “Ͱ͢·͢” …etc

43. There is a wonderful tool for typos and errors

44. wonderful tool: textlint https://textlint.github.io/

45. Summary

46. ❖ Make products first (Code is written first) ❖ Set

    a firm schedule and proceed steadily ❖ As much time for review as possible

47. I hope you produce some great technical books!

48. Publicity

49. We’re hiring Lead members!! It’s a new logo

50. There are three funny system ‣ Unlimited paid holidays ‣

    We all are CEO ‣ Salary is self-determined
51. None
52. None