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
Faking Coherence for Engineers
Search
Yvonne Lam
May 24, 2017
Technology
0
70
Faking Coherence for Engineers
Chefconf 2017 session
Yvonne Lam
May 24, 2017
Tweet
Share
More Decks by Yvonne Lam
See All by Yvonne Lam
So You Want To Get Started in Open Source: Advice for the Non-Normative
yzl
0
300
Get Up Again (Over and Over): Learning and Relearning with Chef
yzl
0
140
Other Decks in Technology
See All in Technology
Simplifying Cloud Native app testing across environments with Dapr and Microcks
salaboy
0
160
CoRL 2025 Survey
harukiabe
1
200
業務効率化をさらに加速させる、ノーコードツールとStep Functionsのハイブリッド化
smt7174
2
140
エンタメとAIのための3Dパラレルワールド構築(GPU UNITE 2025 特別講演)
pfn
PRO
0
330
速習AGENTS.md:5分で精度を上げる "3ブロック" テンプレ
ismk
6
1.6k
React19.2のuseEffectEventを追う
maguroalternative
0
260
AI時代こそ求められる設計力- AWSクラウドデザインパターン3選で信頼性と拡張性を高める-
kenichirokimura
3
320
なぜAWSを活かしきれないのか?技術と組織への処方箋
nrinetcom
PRO
5
920
セキュアな認可付きリモートMCPサーバーをAWSマネージドサービスでつくろう! / Let's build an OAuth protected remote MCP server based on AWS managed services
kaminashi
3
330
Performance Insights 廃止から Database Insights 利用へ/transition-from-performance-insights-to-database-insights
emiki
0
280
Wasmのエコシステムを使った ツール作成方法
askua
0
180
【Kaigi on Rails 事後勉強会LT】MeはどうしてGirlsに? 私とRubyを繋いだRail(s)
joyfrommasara
0
270
Featured
See All Featured
Fantastic passwords and where to find them - at NoRuKo
philnash
52
3.4k
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.9k
Speed Design
sergeychernyshev
32
1.2k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
35
3.2k
Scaling GitHub
holman
463
140k
Intergalactic Javascript Robots from Outer Space
tanoku
273
27k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
33
2.3k
Automating Front-end Workflow
addyosmani
1371
200k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
55
3k
Testing 201, or: Great Expectations
jmmastey
45
7.7k
Rebuilding a faster, lazier Slack
samanthasiow
84
9.2k
[RailsConf 2023] Rails as a piece of cake
palkan
57
5.9k
Transcript
Faking Coherence for Engineers Yvonne Lam (@yvonnezlam) 24 May 2017
Me (@yvonnezlam) • Release Engineer at Chef (Engineering Services) •
CI infrastructure, packaging, internal tools • (really) meta
What is coherence? • “Getting the right amount of information
into the available bandwidth.”
Q: Why talk about coherence at all?
A: Coherence makes working together easier; lack of coherence creates
friction.
A. Coherence as (invisible) infrastructure.
How does lack of coherence create friction?
Like what? • Inefficient message passing between humans. • Skewed
perceptions of knowledge, authority, or capability (our own or others’). • Being legible/visible is tied up with value.
Q. Why *faking* coherence?
A: I don’t think incoherence is fixable for once and
for all.
Why not?
None
(Perception of) Coherence depends on conditions of labor.
Other people are incoherent too.
Nature of craft fields.
So what can we do about it?
Tactics and techniques for faking coherence
Psst! You don’t have to adopt these tactics/ techniques all
the time!
Finish your sentences.
Limit repetition.
Use canned responses.
What are canned responses? • Documentation! • “That’s interesting…” •
Conscious use of heuristics.
Corral your conversation.
How to corral conversations? • Sticky notes are your friend.
• Invite specific responses.
Invite specific responses. • “This is a sketch of a
new feature to do X.” • “I would like feedback about content, not spelling or punctuation.” • “Is what I’m saying making sense to you?”
If all else fails, reset the conversation.
Tactics fall into two classes • Don’t go there. •
If you find yourself going there, stop and turn around.
Strategic questions
Who are you talking to? What do they want from
you?
Are you having the right conversations with the right people?
(http://www.thechangeagency.org/circles-of- commitment/)
Is there a different conversation you need to have?
Some different kinds of conversations • Historical: “Why *did* we
switch from X to Y?” • Speculative: “What would be the reason to switch from X to Y?” • Deep technical: cf Julia Evans’ “How to ask good questions” • Affective: “I am unhappy about …”
How much conversational space do you tend to occupy?
Situate yourself.
None
That’s it!