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
Surviving Code Reviews & Tech Interviews
Search
Cecy C.
November 07, 2019
Technology
0
82
Surviving Code Reviews & Tech Interviews
Presented at The Lead Dev Austin Meetup, November 7th, 2019.
Cecy C.
November 07, 2019
Tweet
Share
More Decks by Cecy C.
See All by Cecy C.
LinkedIn Data Breach 2012 Case Study
cecyc
0
4.8k
Vulnerability True: Surviving Brutal Code Reviews and Tech Interviews
cecyc
0
140
The Joy of CSS: RailsConf 2019
cecyc
0
160
RubyConf 2018 Psychology of Fake News
cecyc
0
79
A Retro of Retros: How Sprint Retrospectives Can Be Both Fun and Productive
cecyc
0
140
MONKTOBERFEST 2018: Psychology of Fake News
cecyc
0
66
From Monolith to Microservice: Building APIs with gRPC & golang
cecyc
3
1.7k
Building APIs with GRPC, PHP, and Golang
cecyc
1
510
The Psychology of Fake News (And What Tech Can Do About It)
cecyc
1
57
Other Decks in Technology
See All in Technology
OPENLOGI Company Profile
hr01
0
57k
組み込みアプリパフォーマンス格闘記 検索画面編
wataruhigasi
1
240
[Ruby] Develop a Morse Code Learning Gem & Beep from Strings
oguressive
1
210
C++26 エラー性動作
faithandbrave
2
860
30分でわかるデータ分析者のためのディメンショナルモデリング #datatechjp / 20250120
kazaneya
PRO
1
460
いまからでも遅くないコンテナ座学
nomu
0
170
PHP ユーザのための OpenTelemetry 入門 / phpcon2024-opentelemetry
shin1x1
3
1.6k
20241228 - 成為最強魔法使!AI 實時生成比賽的策略 @ 2024 SD AI 年會
dpys
0
250
12 Days of OpenAIから読み解く、生成AI 2025年のトレンド
shunsukeono_am
0
810
watsonx.ai Dojo #5 ファインチューニングとInstructLAB
oniak3ibm
PRO
0
290
大規模言語モデルとそのソフトウェア開発に向けた応用 (2024年版)
kazato
1
210
GitHub Copilot のテクニック集/GitHub Copilot Techniques
rayuron
42
18k
Featured
See All Featured
Bootstrapping a Software Product
garrettdimon
PRO
305
110k
Unsuck your backbone
ammeep
669
57k
Build your cross-platform service in a week with App Engine
jlugia
229
18k
Java REST API Framework Comparison - PWX 2021
mraible
28
8.3k
Raft: Consensus for Rubyists
vanstee
137
6.7k
Building Your Own Lightsaber
phodgson
104
6.1k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
44
6.9k
Embracing the Ebb and Flow
colly
84
4.5k
Practical Orchestrator
shlominoach
186
10k
Agile that works and the tools we love
rasmusluckow
328
21k
Art, The Web, and Tiny UX
lynnandtonic
298
20k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
33
2.7k
Transcript
Surviving Code Reviews & Tech Interviews Cecy Correa // @cecycorrea
// The Lead Dev Austin Meetup November 2019 1 Surviving Code Reviews & Tech Interviews {vulnerability: true}
Hi, I’m Cecy! @cecycorrea Surviving Code Reviews & Tech
Interviews 2
I want to talk about vulnerability & failure 3 Surviving
Code Reviews & Tech Interviews
code reviews & tech interviews Surviving Code Reviews & Tech
Interviews 4
Code Reviews Building bullet proof PRs 5 Surviving Code Reviews
& Tech Interviews
6 Surviving Code Reviews & Tech Interviews
Why does this happen?
How does it make you feel? 8 Surviving Code Reviews
& Tech Interviews
Find a way to get control back 9 Surviving Code
Reviews & Tech Interviews
Create a bullet-proof pull request 10 Surviving Code Reviews &
Tech Interviews
DISTRACTIONS 11 Surviving Code Reviews & Tech Interviews
Presentation theme goes here Bullet-proof PRs • Make your PR
as small as possible • Provide context • Provide visuals (where applicable) 12 Surviving Code Reviews & Tech Interviews
Small PRs aka Extreme Slicing EXTREME SLICING is the practice
of breaking down a task into its smallest possible sub-tasks 13 Surviving Code Reviews & Tech Interviews SMOL BOI
Presentation theme goes here Put your PR in Context •
Context is king • JIRA / Trello / ticket • Problem you’re solving • Solution 14 Surviving Code Reviews & Tech Interviews THE CONTEXT KING
Surviving Code Reviews & Tech Interviews 15
Bullet-proof PRs •Are small •Provide context 16 Surviving Code Reviews
& Tech Interviews
Presentation theme goes here What if that still doesn’t work?
17 Surviving Code Reviews & Tech Interviews
It’s part of a larger systemic issue Surviving Code Reviews
& Tech Interviews 18
Surviving Code Reviews & Tech Interviews 19
How do we collectively improve? Surviving Code Reviews & Tech
Interviews
Presentation theme goes here Define success as a team 21
Surviving Code Reviews & Tech Interviews
Establish a team Operating System Surviving Code Reviews & Tech
Interviews 22
“The ultimate goal is to improve the quality of the
code and the product, and any unpleasant tones of one-upmanship should be avoided. Remember that the code is not the author and the author is not the code. Do not take or make things personal.” 23 Surviving Code Reviews & Tech Interviews
Codify as a team how to provide feedback Surviving Code
Reviews & Tech Interviews 24
Feedback should be actionable Surviving Code Reviews & Tech Interviews
25
Feedback should be in context Surviving Code Reviews & Tech
Interviews 26
Feedback should not do the work for someone Surviving Code
Reviews & Tech Interviews 27
A note on “assume positive intent”
assume positive intent == burden on the receiver
assume people are smart competent here for a reason
Bullet-proof PRs •Are small •Provide context 31 Surviving Code Reviews
& Tech Interviews
Good feedback •Actionable •In context •Sets people on the right
path 32 Surviving Code Reviews & Tech Interviews
</code reviews>
Tech interviews Surviving Code Reviews & Tech Interviews 34
The rule about technical interview club is… Surviving Code Reviews
& Tech Interviews 35
Surviving Code Reviews & Tech Interviews 36
Surviving Code Reviews & Tech Interviews 37
Surviving Code Reviews & Tech Interviews
People perform inconsistently Surviving Code Reviews & Tech Interviews 39
Surviving Code Reviews & Tech Interviews 40
People suck at gauging their own performance Surviving Code Reviews
& Tech Interviews 41
Surviving Code Reviews & Tech Interviews
"When people think they did poorly, even if they actually
didn’t, they may be a lot less likely to want to work with you.” Surviving Code Reviews & Tech Interviews 43
Improving the tech interview experience
Hiring at Thinkful •Take home code challenge •Talk through solution
•Add a feature •Open ended architecture
Start the interview by establishing a baseline
Fix tech interview process? Prioritize hiring.
Thank you