Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
The Failure story through writing the first tec...
Search
kkeeth
December 21, 2020
Technology
0
79
The Failure story through writing the first technical book
kkeeth
December 21, 2020
Tweet
Share
More Decks by kkeeth
See All by kkeeth
とある EM の初めての育休からの学び
clown0082
1
1.4k
The history of Javascript frameworks: changes in front-end design philosophy
clown0082
2
140
Visually experience the beauty of mathematics with p5.js
clown0082
1
2.8k
Rediscover the joy of coding with Creative Coding
clown0082
0
1.5k
全員が意思決定する会社で開発者体験や生産性を見る大変さについて
clown0082
0
580
JavaScript × Mathematics go to Digital Art
clown0082
1
340
In-house study group at YUMEMI
clown0082
0
180
Playing Ionic Logo by p5.js
clown0082
0
240
Skills that employers recommend students to acquire
clown0082
1
280
Other Decks in Technology
See All in Technology
ESXi で仮想化した ARM 環境で LLM を動作させてみるぞ
unnowataru
0
150
実は強い 非ViTな画像認識モデル
tattaka
1
900
偏光画像処理ライブラリを作った話
elerac
1
150
JEDAI Meetup! Databricks AI/BI概要
databricksjapan
0
300
白金鉱業Meetup Vol.17_あるデータサイエンティストのデータマネジメントとの向き合い方
brainpadpr
7
970
日経のデータベース事業とElasticsearch
hinatades
PRO
0
180
PHPで印刷所に入稿できる名札データを作る / Generating Print-Ready Name Tag Data with PHP
tomzoh
0
180
短縮URLをお手軽に導入しよう
nakasho
0
130
次世代KYC活動報告 / 20250219-BizDay17-KYC-nextgen
oidfj
0
460
なぜ私は自分が使わないサービスを作るのか? / Why would I create a service that I would not use?
aiandrox
0
910
【5分でわかる】セーフィー エンジニア向け会社紹介
safie_recruit
0
18k
脳波を用いた嗜好マッチングシステム
hokkey621
0
260
Featured
See All Featured
A Modern Web Designer's Workflow
chriscoyier
693
190k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
47
5.2k
The Invisible Side of Design
smashingmag
299
50k
Designing on Purpose - Digital PM Summit 2013
jponch
117
7.1k
Six Lessons from altMBA
skipperchong
27
3.6k
Visualization
eitanlees
146
15k
Fireside Chat
paigeccino
34
3.2k
Documentation Writing (for coders)
carmenintech
67
4.6k
4 Signs Your Business is Dying
shpigford
182
22k
Designing for humans not robots
tammielis
250
25k
A Philosophy of Restraint
colly
203
16k
Rails Girls Zürich Keynote
gr2m
94
13k
Transcript
The Failure story through writing the first technical book kkeeth
@kuwahara_jsri @clown0082 Dec 21, 2020 #ٕज़ॻք۾ΛΓ্͛Δձ
Jun 19, 2020
Published a Riot.js book
Published a Riot.js book Please buy it https://www.amazon.co.jp/gp/product/4863543115
None
...and my happy was for a moment
https://github.com/kkeeth/riot4-book-support/issues?q=is%3Aissue+is%3Aclosed
incoming many misspellings and typographical issues…
OMG !!
What was the problem? What was I supposed to do?
So, today I’d like to share some tips for writing
technical books
Who am I ?
const my_info = { Workplace: ‘Yumemi Inc’, Position1: ‘Servant Leader
of FET’, Position2: ‘Director’, Community: ‘Riot.js, Ionic, DIST’, PokemonGO: ‘TL40’ } About me
npm/~kkeeth
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!!
Analyze why this happened
ɾAbout writing env ɾWhat’s the stats ? Premise
My writing environment
https://docs.gitbook.com/ main tool used
usage about gitbook-cli
usage about gitbook-cli build for static HTML files
my book sample
One problem comes up when I'm writing
I want to count the number of characters…
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.
You just have to make it, someone said
https://www.npmjs.com/package/wcmd created tool
created tool single file multiple files
My writing stats
ɾmy book has 334 pages ɾ230734 characters ɾabout 2 months
ɾmy book is sole author my writing stats
more details https://note.com/clown0082/n/n7549641e5a9e
ɾBug in product ɾNot enough time for review ɾTypographical errors
ɹand misprints Problems
Cause of the problems
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
Points: Make a firm plan and proceed steadily
Review & Fix Writing planning writing project Product Story
Review & Fix Writing planning writing project Product Story Books
usually have a story (my book is too)
ɾ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
ɾ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
Review & Fix Writing planning writing project Product Story At
first, we must get a review ❗ Next, get a review as well ❗
Review & Fix Writing planning writing project Product Story There
are several perspectives, especially here ✋
ɾTypos and errors ɾCapitalize the beginning of nouns ɾConcrete rather
than abstract ɾAmbiguous expression ɾFormatting e.g. “Ͱ͢·͢” …etc
There is a wonderful tool for typos and errors
wonderful tool: textlint https://textlint.github.io/
Summary
❖ Make products first (Code is written first) ❖ Set
a firm schedule and proceed steadily ❖ As much time for review as possible
I hope you produce some great technical books!
Publicity
We’re hiring Lead members!! It’s a new logo
There are three funny system ‣ Unlimited paid holidays ‣
We all are CEO ‣ Salary is self-determined
None
None