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
Working on Wordsmithing
Search
Ryn Daniels
August 23, 2017
Technology
0
180
Working on Wordsmithing
Presented at Write/Speak/Code 2017
Ryn Daniels
August 23, 2017
Tweet
Share
More Decks by Ryn Daniels
See All by Ryn Daniels
Dungeons and Devops
ryndaniels
0
46
untitled config game
ryndaniels
1
2.6k
Designing Sustainable Ops Cultures
ryndaniels
0
1.7k
CI/CD: More than Just Code
ryndaniels
0
330
Building Bridges with Devops
ryndaniels
0
1.7k
Heretical Resilience
ryndaniels
0
2k
Building a Brand
ryndaniels
0
130
Effective Devops and Engineering Culture
ryndaniels
2
440
Put Some Dev in Your Devops
ryndaniels
0
1.8k
Other Decks in Technology
See All in Technology
CDK対応したAWS DevOps Agentを試そう_20260201
masakiokuda
1
320
Kiro IDEのドキュメントを全部読んだので地味だけどちょっと嬉しい機能を紹介する
khmoryz
0
200
データの整合性を保ちたいだけなんだ
shoheimitani
8
3.1k
予期せぬコストの急増を障害のように扱う――「コスト版ポストモーテム」の導入とその後の改善
muziyoshiz
1
1.9k
What happened to RubyGems and what can we learn?
mikemcquaid
0
300
CDKで始めるTypeScript開発のススメ
tsukuboshi
1
460
フルカイテン株式会社 エンジニア向け採用資料
fullkaiten
0
10k
量子クラウドサービスの裏側 〜Deep Dive into OQTOPUS〜
oqtopus
0
120
Data Hubグループ 紹介資料
sansan33
PRO
0
2.7k
GitHub Issue Templates + Coding Agentで簡単みんなでIaC/Easy IaC for Everyone with GitHub Issue Templates + Coding Agent
aeonpeople
1
240
インフラエンジニア必見!Kubernetesを用いたクラウドネイティブ設計ポイント大全
daitak
1
370
Agile Leadership Summit Keynote 2026
m_seki
1
630
Featured
See All Featured
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
196
71k
エンジニアに許された特別な時間の終わり
watany
106
230k
Git: the NoSQL Database
bkeepers
PRO
432
66k
Navigating Team Friction
lara
192
16k
svc-hook: hooking system calls on ARM64 by binary rewriting
retrage
1
100
Building Flexible Design Systems
yeseniaperezcruz
330
40k
Building the Perfect Custom Keyboard
takai
2
690
The untapped power of vector embeddings
frankvandijk
1
1.6k
How to build a perfect <img>
jonoalderson
1
4.9k
Music & Morning Musume
bryan
47
7.1k
Learning to Love Humans: Emotional Interface Design
aarron
275
41k
Agile Actions for Facilitating Distributed Teams - ADO2019
mkilby
0
110
Transcript
Working on Wordsmithing Ryn Daniels Write/Speak/Code 2017
@rynchantress w/s/c 2017 Ryn Daniels they/them - @rynchantress Infrastructure Ops
Witch, Travis CI
@rynchantress w/s/c 2017 professional writing
@rynchantress w/s/c 2017 professional != formal
Let’s get going.
@rynchantress w/s/c 2017 What do we write?
@rynchantress w/s/c 2017 short long formal informal
@rynchantress w/s/c 2017 short long formal informal Chat Books Conference
abstracts Talk proposals Resumés Blog posts Pull requests Project proposals Work emails Code reviews Code comments Cover Letters Retrospectives
@rynchantress w/s/c 2017 good writing provides useful, timely information that
the reader needs.
@rynchantress 3 2 1 w/s/c 2017 agenda PREPARING: IDENTIFYING CONTENT
WRITING: PROCESS AND STYLE REVIEWING: FEEDBACK AND EDITING
@rynchantress w/s/c 2017 Preparing: identifying content
@rynchantress w/s/c 2017 Content: WHAT are you trying to communicate?
@rynchantress w/s/c 2017 what is the outcome I want from
the people who read this? Ask yourself:
@rynchantress w/s/c 2017 which people do i want (or need)
to read this? Ask yourself:
@rynchantress w/s/c 2017 identify your audience
@rynchantress w/s/c 2017
@rynchantress w/s/c 2017
@rynchantress w/s/c 2017 woah that’s a lot of text!
None
@rynchantress w/s/c 2017 Writing: Process and style
@rynchantress w/s/c 2017 start with a summary (or a tl;dr)
None
@rynchantress w/s/c 2017 create an outline
None
None
@rynchantress w/s/c 2017 break content into sections
(pay attention to attention spans)
@rynchantress w/s/c 2017 blargh
None
@rynchantress w/s/c 2017 making information usable
@rynchantress w/s/c 2017 include examples
@rynchantress w/s/c 2017
None
@rynchantress w/s/c 2017 include different levels of content
@rynchantress w/s/c 2017
@rynchantress w/s/c 2017 err on the side of more information
@rynchantress w/s/c 2017 blargh cat tax!
@rynchantress w/s/c 2017 finding your style
@rynchantress w/s/c 2017 Style guides! (not the code kind)
@rynchantress w/s/c 2017
@rynchantress w/s/c 2017 read the backscroll
@rynchantress w/s/c 2017 short long formal informal Chat Books Conference
abstracts Talk proposals Resumés Blog posts Pull requests Project proposals Work emails Code reviews Code comments Cover Letters Retrospectives
@rynchantress w/s/c 2017 Reviewing: Feedback and Editing
@rynchantress w/s/c 2017 blargh
@rynchantress w/s/c 2017 getting feedback
@rynchantress w/s/c 2017
@rynchantress w/s/c 2017 specific feedback groups •Cheerleaders •Critical eyes •Subject
matter experts •Non-SMEs •Your target audience •Your heroes
@rynchantress w/s/c 2017 blargh don’t read the comments
@rynchantress w/s/c 2017 The editing process
@rynchantress w/s/c 2017 •Write •Read through once (and spellcheck!) •Re-read
tricky sections •Wait X amount of time •Internal Feedback •External Feedback •Publish/Send! Repeat as needed }
@rynchantress w/s/c 2017 how much is “as needed”? How much
time is “x”?
@rynchantress w/s/c 2017 Value Axis 0 50 100 150 200
April May June July August September Length/formality of document Time spent editing
@rynchantress w/s/c 2017 Length/formality of document Number of cat pictures
0 50 100 150 200 April May June July August September
@rynchantress w/s/c 2017
@rynchantress w/s/c 2017 don’t let the perfect be the enemy
of the good.
Cat Tax
@rynchantress w/s/c 2017 tl;dr
@rynchantress w/s/c 2017 •Identify audience and takeaways •Write some words!
•Ask for and get feedback •iterate (and iterate) and ship •Keep practicing
@rynchantress w/s/c 2017 Thank you!