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
34
untitled config game
ryndaniels
1
2.4k
Designing Sustainable Ops Cultures
ryndaniels
0
1.6k
CI/CD: More than Just Code
ryndaniels
0
310
Building Bridges with Devops
ryndaniels
0
1.6k
Heretical Resilience
ryndaniels
0
1.9k
Building a Brand
ryndaniels
0
120
Effective Devops and Engineering Culture
ryndaniels
2
430
Put Some Dev in Your Devops
ryndaniels
0
1.7k
Other Decks in Technology
See All in Technology
新アイテムをどう使っていくか?みんなであーだこーだ言ってみよう / 20250911-rpi-jam-tokyo
akkiesoft
0
160
Codeful Serverless / 一人運用でもやり抜く力
_kensh
7
370
大「個人開発サービス」時代に僕たちはどう生きるか
sotarok
20
9.7k
Language Update: Java
skrb
2
290
AIのグローバルトレンド2025 #scrummikawa / global ai trend
kyonmm
PRO
1
260
CDK CLIで使ってたあの機能、CDK Toolkit Libraryではどうやるの?
smt7174
4
110
これでもう迷わない!Jetpack Composeの書き方実践ガイド
zozotech
PRO
0
300
2025年になってもまだMySQLが好き
yoku0825
8
4.6k
Autonomous Database - Dedicated 技術詳細 / adb-d_technical_detail_jp
oracle4engineer
PRO
4
10k
下手な強制、ダメ!絶対! 「ガードレール」を「檻」にさせない"ガバナンス"の取り方とは?
tsukaman
2
420
開発者を支える Internal Developer Portal のイマとコレカラ / To-day and To-morrow of Internal Developer Portals: Supporting Developers
aoto
PRO
1
440
フルカイテン株式会社 エンジニア向け採用資料
fullkaiten
0
8.7k
Featured
See All Featured
How to Ace a Technical Interview
jacobian
279
23k
StorybookのUI Testing Handbookを読んだ
zakiyama
31
6.1k
Product Roadmaps are Hard
iamctodd
PRO
54
11k
Producing Creativity
orderedlist
PRO
347
40k
Why You Should Never Use an ORM
jnunemaker
PRO
59
9.5k
Into the Great Unknown - MozCon
thekraken
40
2k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
131
19k
Designing for Performance
lara
610
69k
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
kevinliebholz
34
6k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.9k
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!